I saw you edited the 'Pagina', but you should edit an 'Inactive' group. This is how we set it up, with blocks. Wich we load up via code in the 'Pagina' if we want to use it.
In my video you see I edit 'Dropdown items', not 'Pagina'.
Thank you for sticking with me. I think this might be it.
So I need to set all my "sub" flexible groups to Expert I guess?
Anyhow, I have addressed this problem multiple times now, and you are the first to stick with me and get to the bottom of this.
But why all the sudden is this a bug? I never had this before, before the change on the plugin end to translate all ACF groups stuff etc.
WHY does it translate the slugs of the field, that should not be possible in my opinion.
Please make sure the field groups are set to Expert mode.
You're creating the field groups using local JSON, and based on what we see, the issue may stem from one of two things:
- Incorrect translation preferences set in two different places for content fields, or
- The use of content as a field name, which can cause conflicts.
Here's what might be happening on your side:
* You created a field group and added a field named content.
* The field group is set to “Same Fields Across Languages.”
* In your ACF JSON, you've configured the fields to be translatable using:
"wpml_cf_preferences": 2,
* You've defined the sub-fields and configured them accordingly.
* When sub-fields are updated, only their JSON gets updated — the main field group JSON does not.
* As a result, when the post is updated, it pulls preferences from the outdated main field JSON, potentially treating content as translatable, this fields has sub-fields name saved and it's gets translated too.
These are just assumptions, for us it works without any issues.
Possible solutions:
* Switch to Expert mode, as mentioned earlier.
* Ensure the JSON files are writable, and set the content field to Copy instead of Translate.
* Whenever you update sub-fields, also update the main field group JSON to keep everything in sync.
