Conditional Logic breaks on front-end form flexible content layouts

Hello,

Thanks for the report. This problem has been reported and will be fixed in the next patch. See Trello Task: https://trello.com/c/w6owa6vr/187-dynamic-forms-repeaters-with-conditional-logic-in-sub-fields-arent-working-correctly-in-the-front-end-due-to-front-end-js-featur

For your information, this bug was introduced in the last patch, in an effort to allow conditional logic to work with custom ACF Form HTML render in the Dynamic Forms UI. In fact, out of the box, ACF conditional logic doesn’t work with it.

For example, this code wasn’t working with ACF conditional logic:

<div class="my-class">
    <div class="acf-field acf-field-checkbox ...">
        <div class="acf-input">...</div>
    </div>
</div>

<div class="my-class">
    <div class="acf-field acf-field-text ...">
        <div class="acf-input">...</div>
    </div>
</div>

The implementation of this enhancement introduced the problem you described with complex fields like repeaters & flexible content. The next patch will fix that.

In the meantime, you can apply the fix by yourself with this insctructions:

In the file acf-extended/assets/acf-extended-form.js line:43. Replace:

var field = acf.getField( rule.field );

With:

var field = target.getField( rule.field );

// ACF Extended: Check in all form if targeted field not found
if( target && !field ) {

    var field = acf.getField( rule.field );

}

Have a nice day!

Regards.

That’s marvelous news! Looking forward to the fix!

Also, may I say: I love you Trello gifs. ??

Cheers!
David

Had the same issue but the solution offered by @hwk-fr solved. I am really a big fan of acf-extended and @hwk-fr, the author. You turn take acf on a whole other level. keep on buddy…

• This reply was modified 4 years, 9 months ago by michnet.