Background of the issue:
Our client has reported multiple occasions where their flexible content fields are gone after copying over content to another language. We have fixed the issue multiple times by setting all ACF fields to 'Copy once' in the 'Custom Fields Translation' WPML setting. The site also has ACF extended installed and also has acf-json Autosync enabled. At the moment the issue is fixed but our client wants to prevent it from happening again in the future. It is hard to replicate the issue if we do not know what is causing it. Let me know if you need any extra access to a staging environment to debug further.
Symptoms:
Flexible content fields are gone after copying over content to another language.
Questions:
How can we prevent flexible content fields from disappearing after copying content to another language?
Is this issue related to WPML or ACF?
Do you need access to a staging environment to debug further?
I don't see here any problem with ACF Multilingual. Settings a custom field to Copy Once will lead to the result you are getting.
From our documentation:
Copy Once: Copies the field value to translations just once, allowing you to independently modify the field values in translations afterward.
In other words, you will see the values from the field set to Copy Once the first time you translate the post. And the next time, it will not be there.
Please also notice that if you pick this option because you want different field values across languages, you’ll need to manually translate posts with these fields in the WordPress editor.
If you always want the same value for the fields in question, you must set them to Copy. Or set them to Translate, which will make your custom field values available for translation.
Please let me know if you have any further questions.
Regards,
Itamar.
The topic ‘[Closed] ACF Flexible content fields not translating’ is closed to new replies.
