SOLVED: Managing ACF Flexible content and clone are broken with bricks theme active

Bugs
1

Browser: Chrome 120.0.6099.200
OS: Windows .

Dear Bricks support,

I’d like to report an issue:
Managing ACF Flexible content and clone are broken with bricks theme active.

Happen in ACF Pro custom fields edit screen.

This looks exactly the same with issue in this thread: SOLVED: Bricks breaks ACF repeater and clone field
It was happened with repeater. but in my case its happen in flexible content. the
So the bug replication procedure should be similar.

The theme and ACF plugin are latest versions
happen in bricks: 1.9.5 (also happen in 1.9.4)
ACF Pro 6.2.4

I think this bug is dangerous because when you managing ACF fields with bricks theme active, and not aware with this clone anomalies, then fixing those ACF fields will further corrupting the ACF setup.

Screenshots:

broken-merged
broken-merged1141×1346 103 KB

Could you please advise on this issue.
Thanks in Advance

2

Hi @BayuWorks ,

Thanks for the screenshot.
Do you mean when the Bricks theme is activated, additional fields are added?

Could you please provide a video record of how to replicate this issue?
We would love to fix it if the issue is coming from Bricks.

Regards,
Jenn

3

Hi @itchycode ,

Thanks for checking the issue,

Do you mean when the Bricks theme is activated, additional fields are added?

Yes, When the bricks are activated, the clone fields are incorrectly substituted with subfields to which it refers

I’ve record video to replicate the issue here:

Just need:

  • latest bricks (1.9.5) and ACF pro
  • create ACF field group, eg named ‘hero’
  • create ACF flexible content, and add clone field that point to hero

Here’s the ACF export data like demonstrated in the video

Thank you
BayuWorks

4

Hi @BayuWorks ,

Thank you very much for your time.
I can replicate the issue locally and record it in the bug tracker.

Regards,
Jenn

5

Hi,

We’ve fixed this issue in Bricks 1.9.9 beta, now available as a manual download in your account (see changelog).

Please let us know if you are still experiencing issues.

As with any beta release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.