Dieses Thema ist gelöst. Hier finden Sie eine Beschreibung des Problems und der Lösung.
Problem: The client is experiencing issues with setting the correct translation behavior for ACF fields in WPML. Specifically, they want to change the field settings from 'copy' to 'copy once'. Despite changing field group translation settings, the fields revert back to 'copy'. The 'column-builder' field, a critical flexible content field, and its nested fields are not maintaining the 'copy once' setting as required. Solution: We reviewed the custom fields on the specified page and found that the main field 'column-builder' does not appear directly in the list of custom fields, which is typical for flexible content fields. However, its generated subfields do appear. We compared the WPML behavior of individual elements with their ACF JSON configuration and found that the settings for fields like 'acfe_flexible_toggle', 'acfe_flexible_layout_title', 'custom-colors', and 'background__layout' are correctly aligned with their respective WPML settings as 'Translate' or 'Copy once'. If you are experiencing similar issues, we recommend checking the ACF JSON configuration for each field and ensuring it matches the desired WPML setting. If discrepancies continue, please provide specific details about which fields are not behaving as expected so we can investigate further.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, do not hesitate to open a new support ticket at WPML support forum for further assistance.
Dies ist das technische Support-Forum für WPML – das mehrsprachige WordPress-Plugin.
Mitlesen können alle, doch nur WPML-Kunden können hier Fragen veröffentlichen. Das WPML-Team antwortet im Forum an 6 Tagen pro Woche, 22 Stunden am Tag.
Background of the issue:
I am trying to set the correct translation behavior for our ACF fields in WPML. Specifically, I want no field to have the 'copy' setting, but instead to be set to 'copy once'. We attempted to change all field group translation settings from 'Expert' to 'Different fields in all languages' on a Test-Page (versteckter Link). This did not change the necessary field settings we need from "copy" to something else either. The problem is located at this Website: versteckter Link.
Symptoms:
Every time I try to set fields to 'copy once', they revert back to 'copy'. We cannot view and edit all fields at once under 'Settings > Translations Custom Fields' due to the lack of filter or mass-edit options, and loading all fields results in an out-of-memory error. The most critical field affected is 'column-builder', which is a flexible content field and contains almost all of our other fields. We urgently need this field including all fields inside it to never be set to "copy"!
Questions:
How can I permanently fix the issue of fields reverting to 'copy' instead of 'copy once'?
Is there a workaround to set the correct translation behavior for all parent and nested fields?
Based on what we discussed, I recommend managing this field group and the WPML translation preferences through code/JSON rather than the Field Group UI, especially given the large number of fields and the use of Clone fields inside the column-builder.
A good approach would be:
1. Export the existing ACF field group to PHP via **ACF → Tools → Export (PHP)**.
2. Register it using `acf_add_local_field_group()` in a custom plugin or your theme.
3. Remove or deactivate the original field group from the WordPress admin so WPML can properly control the translation settings.
4. Update the `wpml_cf_preferences` values (e.g. changing `1` to `3`) in the generated code/JSON where needed.
Because of the sheer volume of fields and nested Clone fields, it’s possible the UI or JSON sync is timing out or not fully updating the translation preferences. Testing this first on your staging/test environment is definitely the right step.
I’ve created a ticket so we can keep this tracked. If the JSON/code-based approach doesn’t resolve the issue, we can investigate further from there.
Unfortunately, it still doesn't work.
Here's what I did:
– I exported all ACF fields as JSON
– In this JSON, I changed all values from “copy” aka ‘wpml_cf_preferences’: 1 to “wpml_cf_preferences”: 3
– In the WP backend, I moved all ACF fields to the trash + deleted them.
– I imported the modified JSON file.
– WPML worked through it.
BUT: Still the same unwanted “copy” behavior, see e.g. the Offers page, which cannot be customized independently in English in the dyn. Components (versteckter Link)
We have now created a separate installation for this case. Please be sure to log in to this one (same login details): versteckter Link versteckter Link
To identify the issue correctly, could you please send me two screenshots for at least one field that is still behaving as “copy”?
1. A screenshot from the ACF interface showing the field (its name/label).
2. A screenshot from the ACF JSON showing the same field inside the JSON structure.
Yes, here is the file. It was generated using the export dialog “ACF/Tools/Export.”
We need to get this done early this afternoon because our customer can't wait any longer. Otherwise, we'll have to start building a workaround using different software 🙁 I really hope we can find a solution quickly.
I’ve checked the custom fields on the page you mentioned and as far as I see
the main field `column-builder` itself does not appear in the list of custom fields attached to this page (see my screenshot). Only its generated subfields (for example `column-builder_0_column-components_…`) appear during editing. This is normal for flexible content fields, but it means the parent field is not directly visible on the post screen.
For the individual elements you highlighted, I compared their WPML behaviour on the page with the ACF JSON configuration:
* `acfe_flexible_toggle` — in the JSON this field is defined with `wpml_cf_preferences: 2` (Translate), which matches the WPML setting shown on the page.
* `acfe_flexible_layout_title` — also defined with `wpml_cf_preferences: 2` (Translate), and this is consistent with what WPML displays.
* `custom-colors` — the JSON sets this field to `wpml_cf_preferences: 3` (Copy once), and this matches the behaviour visible in WPML.
* `background__layout` — this field is configured as `wpml_cf_preferences: 3` (Copy once), which again corresponds to the WPML setting shown on the page.
So far, the ACF JSON and the WPML configuration are aligned for all these fields.
Could you please let me know which specific field under `column-builder` is showing behaviour that does not match the expected WPML setting, so I can check that one next?
Hi Bruno,
Thank you very much for your support and your response. Please excuse my late feedback. Due to time constraints and not being able to find a solution, as well as strange behavior caused by WPML logic, we decided to switch to Polylang for this project, which is now working well. Thank you again for your time. Have a great week!
Florian
