ACF-Conditional-Taxonomy-Rules
ACF-Conditional-Taxonomy-Rules copied to clipboard
Conditional does not work with multiple OR statements using NOT EQUAL TO TERM ID
If you create 2 conditional statements using OR, and those statements use NOT EQUAL TO TERM ID, then the conditional doesn't work.
It does work if using AND, or if you use EQUAL TO TERM ID.
It seems that using AND instead of OR produces the same result, except for in the case where you'd want to add additional logic to each OR statement.
Term ID doesn't equal X and field Y equals 1. OR Term ID doesn't equal Z and field Y equals 2.
Doing this does not work ^ - the conditional just doesn't seem to run
Thanks for reporting Zack.
I'm not actively supporting this plugin at this point so I am not sure if/when I will get to this issue. Honestly I assumed ACF core would have this integrated at this point. But if I am able to spend some more time here I will make sure this is on my list.
I know WPEngine just bought delicious brains (who had themselves bought ACF) so not sure what the dev roadmap is looking like anymore, but hopefully it is on their list!
Thanks. We'll see if they do a public road map or any kind of feature voting now, but I'm not optimistic since they haven't so far. 🤷🏼♂️