I need help with making ACF fields fully functional on the English version of my site using WPML, in...

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
-	6:00 – 12:00	8:00 – 12:00	6:00 – 12:00	8:00 – 12:00	6:00 – 12:00	-
-	13:00 – 15:00	13:00 – 17:00	13:00 – 15:00	13:00 – 17:00	13:00 – 15:00	-

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

Tagged: Documentation request

This topic contains 1 reply, has 0 voices.

Last updated by Nicolas V. 2 months, 2 weeks ago.

Assisted by: Nicolas V..

Author	Posts
November 14, 2024 at 10:44 am #16401699
justinL-10	Background of the issue: I am trying to translate specific ACF fields on the English version of my site, eaom.growinglemon.nl, using WPML. I need help with making ACF fields fully functional, ensuring fields appear on the front end, images load properly in galleries, and taxonomy filters work without language conflicts. I have checked WPML settings, ensured fields are marked as 'Translate' or 'Copy,' and used String Translations. hidden link (has pictures and Adres) hidden link (has no pictures and no adres) I've translated all pictures aswell. Symptoms: The ACF field 'Adres' (Address) does not appear on the front end in the English version. The project gallery images are not showing up on the English site. When filtering by taxonomy in English, the custom field changes back to Dutch instead of displaying in English. Questions: How can I make the ACF field 'Adres' appear on the front end like the other custom fields in the loopgrid and project page in the English version? Why are the project gallery images not showing up on the English site? How can I ensure that taxonomy filters display in English with english fields without reverting to Dutch? hidden link
November 14, 2024 at 3:29 pm #16403826
Nicolas V. Supporter Languages: English (English ) French (Français ) Timezone: America/Lima (GMT-05:00)	Hello, Welcome to the WPML support forum. I've noticed in your debug info that several locked settings have been modified: [acf-field-group] [acf-post-type] [acf-taxonomy] Those custom post types are now translatable, which can cause issues. Here we will focus on [acf-field-group] to solve your ACF fields issue. 1. In "WPML > Settings > Post Type Translation" the "Field Groups (acf-field-group)" preference should be "Not Translatable". 2. Now when you edit your ACF group in the default language in "ACF > Field Groups", this is where you determine the translation preference for each field. Here we are talking about the translation of the field value. Ref: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/ We have 3 multilingual configuration options: - Same fields across languages > To be used in most cases. - Different fields across languages > Only if you want totally different fields between your languages and you are using the WordPress editor. - Expert Mode > Which allows you to choose the translation preference for each field Be careful though because some fields must have specific preferences. Please read our documentation: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/ I would recommend here to start with "Same fields across languages" and later, if you need to make small adjustment on the translation preferences, you can switch to expert mode.

The topic ‘[Closed] I need help with making ACF fields fully functional on the English version of my site using WPML, in…’ is closed to new replies.