Skip Navigation

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

Problem:
The client was experiencing an issue where links inserted in the ACF WYSIWYG editor were not pointing to their translated content.

Solution:
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.

No supporters are available to work today on this forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Tagged: 

This topic contains 18 replies, has 2 voices.

Last updated by Carlos Rojas 10 months, 3 weeks ago.

Assisted by: Carlos Rojas.

Author Posts
December 7, 2023 at 4:05 pm #15019029

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Thank you for sharing this information. I can see the issue happening.

Could you update 'Advanced Custom Fields PRO' plugin to the latest version and double-check if the issue persists?

December 7, 2023 at 4:18 pm #15019051

jmcb-communicationB

Updated ACF Pro and ran a scan. Also made a minor change on an article and update translations. Problem still persists.

Please have a look at this site -> hidden link

Same structure, same plugins and this one works fine (without the XML config) ...

December 8, 2023 at 10:35 am #15024637

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Thank you for your message.

I have escalated this new issue to our specialists in the 2nd tier so then can take a deeper look. I will get back to you as soon as I get an answer.

December 19, 2023 at 11:04 am #15091569

jmcb-communicationB

Hello Carlos,

Any news on this issue ?

Thanks !

December 26, 2023 at 7:11 am #15128275

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Hi there,

Our 2nd tier specialists are still working on a solution for this issue. I will get back to you as soon as possible.

Thank you very much for your patience and understanding!

December 29, 2023 at 9:34 am #15136151

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Hi there,

All WYSIWYG ACF fields are registered correctly and the links outside these fields are already adjusted. If you find any untranslated links you just need to update the translation.

Have an excellent day!