Unable to use both XLIFF import/export functionality and automatic translations.

This thread is resolved. Here is a description of the problem and solution.

Problem:

The client is facing issues with missing ACF fields in automatic translations due to conflicting translation preferences between XLIFF import/export and the Advanced Translation Editor. The fields are set to 'Translate' for XLIFF but need to be 'Copy' or 'Copy Once' for the editor, causing discrepancies in the translated content.

Solution:

We recommend the following steps to address the issue:

1) Open the post for editing.
2) Scroll to the bottom and locate the 'Multilingual Content Setup' section.
3) Change the translation preference of the ACF fields from 'Copy once' to 'Copy'.
4) Click 'Apply' to save the changes.
5) Make a minor change in the content of the original post.
6) Update the post.
7) Update the translation accordingly.

If this solution does not resolve your issue or seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance at WPML support forum.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Bug

This topic contains 1 replies, has 0 voices.

Last updated by Bigul 6 months, 2 weeks ago.

Assisted by: Bigul.

Author	Posts
July 14, 2025 at 5:25 pm
peter-rF	Background of the issue: Our site is built with a custom theme by an agency using ACF fields like 'Group', 'Clone', 'Flexible Content', 'Tab', 'Accordion', and 'Repeater'. We have implemented translation functionality to export and import content for translation with TransPerfect. We want to test automatic translations for the rest of the site, but our current setup doesn't allow it. The issue is with how the 'Translation Preferences' are set up for each ACF field, especially structural fields. These fields must be set to 'Translate' for XLIFF import/export, but the Advanced Translation Editor requires them to be set to 'Copy' or 'Copy Once'. This discrepancy is causing issues with missing ACF fields in automatic translations. Symptoms: Missing ACF fields in automatic translations, especially in areas like 'Content Blocks' and 'Lower Content Blocks'. Questions: Is it possible to use both XLIFF import/export functionality and automatic translations with our current setup? How can we resolve the issue with missing ACF fields in automatic translations? Is there a way to adjust the wpml_cf_preferences value for each field without affecting XLIFF import/export? Why are some fields not showing up on the JA page even after adjusting the 'Translation Preference'?
July 14, 2025 at 7:39 pm #17235459
Bigul	Hello, Please try the following steps and make sure it is working as expected. Check the attached image for more details. 1) Open the post for editing - hidden link 2) Scroll to the bottom of the screen and locate the Multilingual Content Setup section 3) Change the translation preference of the ACF fields from Copy once to Copy 4) Click Apply to save the changes 5) Make a minor change in the content of the original post 6) Update the post 7) Update the translation accordingly -- Thanks! Bigul