I’m making extensive use of clone fields in my latest project. I’m also using the acf-json folder to synchronise the field groups from development environment to staging & production servers.
For some reason, I’m getting situations where the cloned field-groups suddenly “expand” within the containing field group.
For example, I have a field group called “button component” which is used in a field group called “text block”. Normally when editing the “text block” field group, I should see a single clone field called “button component”. However, something is happening at some point which is messing things up so that now when editing the “text block” field group, I am seeing ALL the fields from the “button component” within “text block”.
Has anyone got any idea what could be causing this?
Could it be because I am pushing the use of ACF’s clone fields beyond what they can handle?
In this site I am using clone fields to the extreme, for example, having “component” field groups cloned into “block” field groups which are cloned into “section” field groups which are cloned into a flexible content field.
When the problem occurs, I have been able to fix it by deleting ALL the field groups and then re-syncing them again from the .json files, but this seems to be unreliable. Sometimes it works, sometimes it doesn’t.
