Bricks Version: 1.4.0.2 Browser: Chrome 90 OS: macOS / Windows / Linux / etc.
If the theme Bricks is active, then you try to save an ACF group with a repeater field and a clone field inside, on page reload the field appears as the field cloned…I spend hours and hours looking to the problem, and could not imagine it was the theme.
any news on this??? I’m using a base acf fields groups on each site and each time I have this problem… And i need to deactivate the bricks theme each time I want to modify the fields…
First question: Does the problem still occur in Bricks 1.5.4? If yes:
To speed this up, I ask you to send us the exported field group, as Luis did back then, so we can ensure that our setup is exactly the same as yours.
Would either one of you be so kind as to provide a short screencast showing and explaining the issue plus attach the exported field group, so we can try to replicate the issue?
A simple example for clone field is
Add an ACF field Repeater A
In A, add a Group B
In B, add a few fields you want.
Then add an ACF field Repeater C
In C, what you want is exactly the same as Group B. So instead of setting a new Group D and its subfields again, you can just use the Clone field and select Group B.
But in Bricks now, dynamic data from repeater C would not work, while it used to work according to others saying before.