Dynamic Attribute on Archive Pages doesn't work

[Jonas]

Description:

I want to use the value of an ACF field as attribute on my category archive page. The dynamic content rule that works for dynamic text does not work for the dynamic attribute.

These are the settings for a paragraph (this works):

These are the settings for the dynamic attribute (doesn’t work):

Environment info

• WordPress version: latest
• Cwicly Plugin version: latest

[StrangeTech]

@Jonas

These are the settings for the dynamic attribute (doesn’t work):

Which block are you applying this to? The reason I ask:

@StrangeTech

The only limitation we found was it didn’t work in an attribute for a Section block.

We had to use a Div block change the html tag to section and add the default Cwicly Section block attributes to it.

[Jonas]

Thats interesting. I did use a section but for me it doesn’t work with any element I try.

[Jonas]

This also applies to the conditions for Global Fragments. The condition shown in the screenshot does not work on archive pages

[Jonas]

This issue also seems to affect the visibility conditions:

[StrangeTech]

@Jonas

The condition shown in the screenshot does not work on archive pages

I think there may be some kind of misunderstanding for this one. Where are you setting the values for Theme Settings field group Transparent Header property? As the Archive template is not a page, the only thing I can think is that you are adding these directly to the template. We tried that before and it didn’t work, which seems to be an ACF limitation, not a Cwicly one.

I think the only way to do this in a configurable way would be to add it to an ACF Options page.

[Jonas]

Hmm, regarding Global Fragments you might be right. The ACF value I’m looking for is set in the Taxonomy Terms settings. So for example I have the term “Socks” in my shop and in the settings of this Term I set the ACF value.

[StrangeTech]

@Jonas

So for example I have the term “Socks” in my shop and in the settings of this Term I set the ACF value.

Ahh, you are setting it for the terms! In this case I believe at the moment you will only be able to reference it within the context of that term (either within a Taxonomy Terms block, or within a Query block).

However, please see this bug for possible issues and workarounds:

Repeater ACF field added to a Taxonomy Term isn't displaying on Taxonomy archive template

Description: We have an ACF field group associated with a taxonomy called Service that contains a Partners repeater field. We want to display the field on the archive template associated with the taxonomy terms. We have tried putting it directly into the template and tried wrapping a Query around the repeater dynamically using the Archive Taxonomy and Archive Term, to see if that picks up the data but it still doesn’t work. Is the repeater missing a Location option for the current taxonomy t…

[Jonas]

@StrangeTech

Ahh, you are setting it for the terms! In this case I believe at the moment you will only be able to reference it within the context of that term (either within a Taxonomy Terms block, or within a Query block).

Well, I do can reference ACF values in all other ways. I can pull images and dynamic data for text elements for example. So it does seem to be somewhat accessible.

[StrangeTech]

@Jonas

So it does seem to be somewhat accessible.

This was the issue I was highlighting the most.

@StrangeTech

Finally, this same issue also affects visibility conditions, we have had to use a custom function for this also, instead of being able to use the built-in ACF field features:

function service_has_stats() {
	$has_stats = false;
	$term = get_queried_object();
	$stats = get_field( 'stats', $term);
	
	if ( $stats ) {
	  $has_stats = count($stats) > 0;
	}
	return $has_stats;
}

[Jonas]

Ahh, I understand. All these PHP stuff is a bit complicated for me
For now I have a Workaround with CSS that I’m fine with. So I will now wait to see what @Louis thinks about this.

Thanks a lot for your engagement here and in this forum general! Especially you and @Marius are a treasure for this community!