Problem: The client was experiencing issues with custom fields not displaying correctly after translating pages using WPML's Advanced Translation Editor (ATE). The content from some custom fields was serialized in the database, which prevented it from displaying correctly in the WordPress editor. Solution: We identified that the serialization of complex custom field keys in the database was causing the issue. To resolve this, we applied a specific solution from the WPML errata. Here are the steps we followed: 1. Opened the page for editing in the default language (English). 2. Made a minor change in one of the text fields in the "Page problem tab". 3. Saved the changes. 4. Updated the Hebrew and Arabic translations in ATE. 5. Checked the "Page problem tab" fields by switching to Hebrew and Arabic in the WordPress editor to ensure the fields displayed correctly. For existing pages with issues, repeating these steps should resolve the problem. Additionally, we recommend bookmarking the errata page for future reference and subscribing to comments for updates on permanent fixes.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 necessary, please open a new support ticket at WPML support forum for further assistance.
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.
