WPML Advanced Translation Editor Issue with ACF Link Field

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

Problem:
The client was unable to translate a custom link field ('Case Study') associated with a custom post type ('Customer') using WPML's Advanced Translation Editor (ATE), despite having set the ACF fields as translatable.
Solution:
We recommended checking if using the Search option in ATE would return the URLs needed for translation. We also suggested testing with a different ACF field type, specifically the URL field, to see if the issue persists. After further investigation and consultation with our second-tier support, we escalated the issue for deeper analysis. We provided a video guide and an errata page (https://wpml.org/errata/advanced-custom-fields-external-links-are-not-translatable-in-same-fields-across-languages-mode/) explaining the steps to make the link field translatable. Finally, our second-tier specialists confirmed the solution by applying specific code, as shown in another video (https://www.loom.com/share/813a329ec1c54627a3c2e3f5c4ada205).

If this solution does not resolve your issue, or if it seems outdated, 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 the problem persists, please open a new support ticket at WPML support forum.

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.

Tagged: Exception, Known issue

This topic contains 26 replies, has 0 voices.

Last updated by Carlos Rojas 2 weeks, 3 days ago.

Assisted by: Carlos Rojas.

Author	Posts
May 18, 2026 at 12:12 pm #18042837
justinb-4	Hi, We have a custom post type called Customer, and we’ve attached several ACF fields to it. One of those fields is a link field called Case Study. In the original language (English), we can add a value to this field and display it as a link on the frontend. However, we would like to use different link values for other languages. Although we have set these ACF fields as translatable in the ACF field settings, the Case Study link field does not appear in the WPML Advanced Translation Editor for the translated version. I’ve explained the issue in the video below. Please take a look and let us know if you have any questions. We’d appreciate your guidance on how to resolve this. hidden link Thank you.
May 18, 2026 at 12:28 pm #18042873
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hello again, The chat was closed because it seems you got disconnected. On the chat, I mentioned that I'd recommend checking if using the Search option in ATE will return the URLs you need to translate. Also, there is another ACF, I think it is called URL, that might not have this problem. I kindly ask you to run a test by creating a custom field with this other field type and check if the issue disappears. Looking forward to your message. Regards, Carlos
May 18, 2026 at 3:11 pm #18043629
justinb-4	Hi, Thank you for your response. The chat was disconnected automatically, so I raised a ticket again. It didn't return the URLS I need to translate in the ATE search option. I created another Link field in the Customer post type, added a value in the original language, and tried to translate it using the WPML Advanced Translation Editor. However, I received an error on the Translation Queue page. Please see the attached screenshot for reference. I tried this multiple times, but I got an error: WPML tried to translate this page three times and failed. To get it fixed, contact WPML support. I’ve also attached a screenshot of the Advanced Translation Editor error log. Please check it and let me know your thoughts. Thanks.
May 19, 2026 at 7:48 am #18044787
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi there, Thank you very much for your feedback 1.- Please share the URL of the content where you added the ACF link and the name of the ACF. 2.- Also, I kindly ask you to share the access credentials to the site in your next message, which I have set private. This will allow me to reproduce the issue in the URL you shared on the previous point and double-check the WPML configuration. Confirm you have created a full site backup that you can restore if necessary. Looking forward to your message.
May 19, 2026 at 9:20 am #18045040
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi, Thank you for creating the staging site Before we continue, I kindly ask you to update all outdated plugins that appear in this link: hidden link and double-check if the issue persists.
May 19, 2026 at 11:43 am #18045613
justinb-4	Hi, I’ve updated all plugins on the staging site. However, when I try to check whether the file field is available in the WPML Advanced Translation Editor, I still can’t access it for any customers in the translation queue. When I click the translate button, it shows an error: ' WPML didn't manage to translate this page.' Please see the attached screenshot for reference. Thanks
May 19, 2026 at 12:17 pm #18045819
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi there, I created a video showing how to translate the link in the Customer CPT: hidden link I kindly ask you to create a similar video describing the other problem related to the Facet plugin. Because I'm not 100% sure of what the problem is.
May 20, 2026 at 10:58 am #18048270
justinb-4	Hi, Thanks for the video. I tried to replicate the solution you mentioned in the video, but I couldn’t proceed because the translation editor wouldn't open for me. I’ve demonstrated the issue in the video below. Please take a look and let me know what might be causing it. hidden link Thanks
May 20, 2026 at 11:24 am #18048416
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi there, I created this video: hidden link describing the steps you need to follow. Also, here you will find the guide I mentioned on the video: hidden link
May 20, 2026 at 12:56 pm #18048706
justinb-4	Hi, Thank you for your video. I created a new staging environment to test your suggestion, as I wanted to follow the recommended steps from the beginning, including making the Link field and the system field translatable from the post edit screen. When I changed the ACF field group setting from “Export” mode to “Same fields across languages,” I expected the option to change 'copy' to 'translate' for the Link field to become available. However, the option to change 'copy' to 'translate' for that specific Link field (i.e., customers_case_study) on the post edit screen remains disabled. I’ve demonstrated this in the video below. Please see the attached screenshot for reference. I’m also still unable to see the Link field in the Advanced Translation Editor. Please check the video and let me know your thoughts. hidden link If you need access to the new staging environment, I’ll be happy to share the credentials. Please send me a private message request, and I’ll provide the details there. Thanks.
May 20, 2026 at 1:01 pm #18048757
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi, Thank you for sharing the video. Yes, I will need access to the staging environment. Your next message will be private so you can securely share the access credentials.
May 21, 2026 at 8:30 am #18050373
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi, Thank you very much for sharing the credentials for the staging site. I consulted this issue with my colleagues, and the recommendation is to escalate to our 2nd tier of support for further testing and investigation. But before I escalate, I kindly ask you to tell me where the CPT Customers were created. My goal is to leave the staging site in a minimal setup (only the WPML plugins, a default WordPress theme). Looking forward to your message.
May 21, 2026 at 9:05 am #18050643
justinb-4	Hi, Thanks for your response. The 'customers' post type is registered in our theme. Thanks!
May 21, 2026 at 10:06 am #18051086
Carlos Rojas WPML Supporter since 03/2017 Languages: English (English ) Spanish (Español ) Timezone: Europe/Madrid (GMT+02:00)	Hi, Thank you for your message I have escalated this ticket to our 2nd tier of support, where our specialists will take a deeper look at this issue and will try to isolate its cause. Please do not delete or edit the staging site, as we are going to continue working on it. I will get back to you as soon as I get more information. Thank you very much for your patience and understanding!
May 21, 2026 at 11:16 am #18051348
justinb-4	Hi, Thank you for the update. Sure! We won't make any changes to the staging site. Looking forward to your response. Thanks!