This thread is resolved. Here is a description of the problem and solution.
The client was experiencing an issue where links inserted in the ACF WYSIWYG editor were not pointing to their translated content.
First, we recommended applying the workaround described in our errata page: Advanced Custom Field links inside WYSIWYG fields are not automatically translated.
When that did not resolve the issue, we suggested the following steps:
1. Create a full backup of the site.
2. Update all outdated plugins.
3. Update the WPML plugins.
4. Flush the cache memory.
5. Edit the post in the original language and make a small change to the content.
6. Save the changes and update the translation.
7. Double-check if the issue disappeared.
After these steps did not fully resolve the problem, we advised running a scan for internal links again. We then converted the chat into a forum ticket for further assistance and potential escalation to our second-tier support.
Additionally, we updated the XML configuration for the custom fields to ensure the correct field names were targeted:
<custom-field action="translate" translate_link_target="1">intro_de_la_page</custom-field>
We instructed the client to edit the content in the original language again, make a small change, update the translation, and then check if the links in that field were updated.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us.
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.
Our next available supporter will start replying to tickets in about 0.34 hours from now. Thank you for your understanding.