Translate input of ACF

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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	-	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00
-	-	-	-	-	-	-

Supporter timezone: America/Lima (GMT-05:00)

This topic contains 3 replies, has 0 voices.

Last updated by Andreas W. 1 year, 1 month ago.

Assisted by: Andreas W..

Author	Posts
February 20, 2025 at 4:05 pm #16730645
dianaR	Background of the issue: I created a custom field with URL input. I want different URLs for each language. In the 'Multilingual Content Setup' of the Field Group, I chose 'Make 'Field Groups' translatable'. Symptoms: I still can't translate the URLs. In 'WPML > Setting > Custom Fields Translation' my custom field is not clickable (is set to 'Copy' but I can't change it). Questions: How can I make my custom field translatable so that I can have different URLs for each language?
February 22, 2025 at 8:51 pm #16736963
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Hello, Correct, the link field is currently by default set to "Copy". Our config still considers it as a field that only returns the link URL and expects that an internal link is used. In this case, the link will point automatically to the translated content once the content that you are linking to has been translated and published. This will not work out of you want to return a link object including a link text and maybe you are even using an external link. In this case you need to set the link field to "Translate". To be bale to change the settings of the fields the ACF Field Groups that contain your link field need to be set to "Expert" mode. After that change the link field to "Translate". The ACF Field Groups should not be set to translatable. Please set the to "Not translate" in WPML > Settings > Post Type Translation" and delete the duplicated versions of your field groups. Make sure to not use the same field name more than once. This could cause a field that is set to "Translate" will not show up inside the WPML Translation Editor. Make also sure that fields like Repeater, Group, or Flexible Content are always set to "Copy" when using the WPML Translation Editor to create the translations. More details you can find in this guide: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/ Best regards Andreas
February 24, 2025 at 4:05 pm #16742063
dianaR	Hi, it's not really clear and what I did, did not work. I upload the screenshots: 1. In my ACF I need to insert different external URLS in each languages 2. I set "Field Groups Not transatable" (WPML > Settings > Post Type Translation) 3. I set "Don't translate" (in ACF) ..in the translator editor, I still can't add a translation.
February 25, 2025 at 5:08 pm #16747228
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	To be able to translate the link field it needs to be set to "Translate". Then, when translating the content with the WPML Translation Editor, you should be able to translate the URL. In doubt use the search field inside the translation editor and search for "http". If you want to use the same link in both languages, set the field to "copy" and apply the translation of the page or post again.

The topic ‘[Closed] Translate input of ACF’ is closed to new replies.