[Resolved] How to ignore previously changed fields in translated posts?
This thread is resolved. Here is a description of the problem and solution.
Problem: The client was facing a problem where changes made directly in the WordPress Editor to ACF fields marked as 'Don't translate' were being overwritten after updating the original content and re-translating it using WPML's Advanced Translation Editor (ATE).
Solution: We recommend sticking to one translation method to avoid this issue. If you're using the WPML Translation Editor, you should avoid manually editing translations in the WordPress Editor, as the WPML Translation Editor cannot recognize those changes and will overwrite them upon re-translation. For fields that you want to manage manually, you should use the ACF Field Group Option 'Different fields in different languages' and translate the content only with the WordPress Editor.
If this solution doesn't seem relevant to your situation, please open a new support ticket with us, and we'll be happy to assist you further.
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.
How to ignore previously changed fields in translated posts?
Hello! At the moment, we are testing WPML on our website and in the process, unpleasant moments were discovered that prevent us from organizing the translation of our articles and pages.
I have attached the screenshots with separate links to make it more convenient.
Most of our content is stored in ACF Pro custom fields. Our field groups are associated with ACF blocks, which are subsequently displayed in the Gutenberg editor (hidden link)
hidden link hidden link
Here's an example of what the content looks like
hidden link
Since we use ACFML, we have the opportunity to specify an option in the custom fields settings that will be responsible for translation. We have the “Introductory text” set to “Translate” because we want to translate this field. The remaining fields are set to “Don't translate”.
hidden link hidden link hidden link
Then, we decided to translate the page through “Translation Management”.
hidden link
Next, we go to the ATE editor by clicking on the gear of the required language.
hidden link
In ATE we see all the content necessary for translation. We translate and complete.
hidden link
In the translated article, we get the expected result, the content has indeed been translated. Also note that the “Anchor links” block also contains values that were copied from the original article, which also suits us.
hidden link
Now we come to the core of our problem. We change the values in the translated (German) page in the “Anchor links” fields, for which we previously specified the “Don't translate” option.
hidden link
After which, on the original (English) page, we edit any content in order to translate it again in the future.
hidden link
We then go back to ATE to translate the new content.
hidden link
Returning to the German page, we see the new translated segment, however, pay attention to the “Anchor links” block, which we previously changed manually, it again has the same meaning as the original (English page). We expected that this content would not be affected if we tried to translate the page again. For us, this is now the main problem that forces our editors to edit the page every time they receive new translations.
hidden link
We also tried setting the custom fields to “Copy” or “Copy once”, but this did not work.
hidden link
Could you help us solve this problem. How can we force WPML to ignore some fields?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
This is indeed expected, as you have to stick with only one translation method.
The translation method is set inside the right sidebar of the WordPress Editor on the original content.
You choose between WPML Translation Editor or WordPress Editor.
If you use the WPML Translation Editor as a translation method you should not manually edit translations inside the WordPress Editor, as the WPML Translation Editor can not recognize those changes and it will overwrite them once you translate the content again using the WPML Translation Editor.
Further, the ACF Field Group translation options "Same fields across languages" or the "Expert" mode are dedicated to translating the content with the WPML Translation Editor.
If you translate the content with the WordPress Editor, you should use the ACF Field Group Option "Different fields in different languages".
---
About internal links:
WPML will always adjust internal links automatically once a translation for content is detected.
