ACF 6.3.0 New Conditional logic rules for fields ERROR

Can’t add rule:

https://www.awesomescreenshot.com/video/28895296?key=108901a06bae89645c8f0f067cdfd581

I’m also encountering an issue with taxonomy conditional logic. Different from yours because i can see a result when i click to choose, saying it can’t find anything. Yours seems like the error I had before when using frontend admin plugin.

By the way conditional logic for taxonomy is not working with the last update

last update is 6.3.2.1

Hi,

I just a did a test and even with Advanced Forms deactivated, I still can’t bring up a list of terms in the field’s conditional logic.

Are you seeing everything work once you deactivate Advanced Forms? Could you possibly create another screencast showing it working and not working in the two different contexts? I might be misunderstanding the issue here – a video will sort me out.

Cheers,
Phil

Hi, @gianlucat is right, last acf version lost conditional taxonomy, I have tried with ACF 6.3.1, please take a look:

https://capture.dropbox.com/9ippHzZbwd3Gi00C

Thanks,
Sebas

Hello, Same for me.
Conditional logic with taxonomy field dont work => javascript error in plugins/advanced-forms/assets/dist/js/admin.js
Its impossible to assign an element into the list “term is equal to”

af: Version 1.9.3.5
acf pro: Version 6.3.5
Wp: Version 6.6.1

NB : I try with advanced form disabled and conditional logic with taxonomy field work.

• This reply was modified 1 month, 3 weeks ago by iskisbzh.

Hi @iskisbzh

I’ve just performed another check with the latest version of ACF and without Advanced Forms in the mix, I can’t get terms appearing in the conditional logic rules at all.

I may not be understanding your situation clearly however, can you please put together a screencast with an explanation that allows me to understand the situation better?

Cheers,
Phil

Ah, thanks. I’m now able to reproduce this one.

I have added this to my list and will look at fixing this ASAP. I can’t give you a timeline at this stage but this will be the focus of the next patch.

Hi all,

I’ve just released 1.9.3.6 which resolves this issue.

Cheers,
Phil