bravotangodev

The acfe_flexible_toggle sub field was added automatically is my best guess – it wasn’t done manually if that is what you are implying. I am not using ACFE Pro. Maybe this was a leftover from a previous version? Not sure.

I think this was just a red herring though, I can see, when using a new layout, it is adding/removing the "toggle" as to acfe_flexible_add_actions as expected; however, the toggle is still not working.

Disabling acf-json is still causing it to work normally. Example: https://dev.bravotango.ca/tests/acfe/toggle.mp4

I tested this previously with the default theme and no other plugins. The default theme worked until I started using Local JSON.

I found the issue. It is because I am using Local JSON in ACF. I discovered this my clearing out the folder and it started to work. After regenerating them, I see that enabling the “Toggle Layout” in the “Additional Actions” does not trigger an update the acf-json.

• This reply was modified 1 year, 9 months ago by bravotangodev.

Some additional information here:

It textdiffed the site with it working/not working and it seems like Gravity Forms fails to load properly is because it is not injecting a lot of its scripts/styles (both inline stuff and enqueued requests) into the website.

Could the render style.css/script.js fields be messing with this somehow?

Yep, I am using “Dynamic Render” as it’s very useful for my ideal workflow (not needing to specify each template/have assets loaded modularly).

Using do_shortcode('[gravityform id="1" title="true"]') after the the_flexible still produces the same issue. When using above the the_flexible it works as expected.

I can confirm using the normal ACF have_rows/the_row method works correctly/as expected. So it seems like it is related to something the_flexible is doing.