Conditional on ACF relationship field doesn't seem to work

Beta
#1

I’m using display conditions to show/hide ACF fields (with great success- thanks!) and have just started using an ACF “relationship” field. When I try to use that field as a display condition it doesn’t seem to work - whether I use “is” or “is not” it doesn’t display. Seems like it’s not recognising that field name as valid.
Not a big deal, but just something to look at in Alexander’s never ending to do list :slight_smile:

SORRY Obviously this is an array type field, probably like a repeater, so I’ll try setting it up with a provider set to “custom”. Obviously didn’t get enough coffee yet today.

#2

Hi @spedney,

No problem! Good news, we’ll be supporting relational fields in the next cycle. You’ll be able to pull that array output into a Looper Provider. Once it’s there, you could use a condition to determine if the looper results are empty or not.

I was playing around with relational fields earlier today and it’s pretty wild what can be built out. When you loop over Posts or Terms from a relational field, that Post or Term becomes the new context for Dynamic Content. That means you can setup a new Looper inside that element that gets ACF fields again, and keep traversing the relationships as far as you want.

1 Like