Problème d’affichage du contenu ACF dans les pages traduites

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

Problem:
The client is experiencing issues with WPML and Advanced Custom Fields (ACF) integration. Specifically, there are problems with translating slugs for dynamic data, which causes the builder not to recognize the translated slug, leading to fields not displaying correctly. Additionally, ACF repeater fields are not displaying data in translated versions of pages, and there is a concern about whether an expired ACF license might affect field translations or syncing.
Solution:
1) Ensure that once ACF field groups are set to 'Same fields in all languages', no further changes should be made to custom fields from WPML > Settings. If changes were made, revert them.
2) Check if the translated content displays correctly in the ACF fields in the backend of the second language page. If it does, the issue might only be occurring on the frontend.
3) For issues with slug translation, despite disabling slug translation in WPML settings, ensure that ACF shortcodes are added to the appropriate widget that does not translate them, such as a shortcode widget in Bricks.
4) For repeater fields not displaying, verify if the content shows in the backend in ACF fields when the page is edited in WP editor, not in bricks.

If these steps do not resolve the issues or if the solution seems outdated or not applicable to your case, 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 problems persist, please open a new support ticket.

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

This topic contains 5 replies, has 0 voices.

Last updated by Dražen 1 month, 2 weeks ago.

Assisted by: Dražen.

Author	Posts
March 11, 2025 at 1:15 am #16798901
sandraB-42	Background of the issue: Je rencontre actuellement un problème avec la traduction de mon contenu généré via Advanced Custom Fields (ACF) en utilisant WPML. J’ai configuré mes groupes de champs ACF en « Champs identiques dans toutes les langues ». Pour les champs individuels, j’utilise les options « Copier » ou « Traduire » dans WPML > Traduction des champs personnalisés selon les besoins. J’ai vérifié et régénéré les traductions en mettant à jour la page d’origine. Symptoms: Sur mes pages en langue par défaut, tous les contenus s’affichent correctement. Cependant, dans les versions traduites, certains éléments ne s’affichent pas du tout, notamment les images ajoutées via un champ ACF et certains contenus textuels. Questions: Pourriez-vous m’indiquer la meilleure pratique à adopter dans ce cas afin que toutes les valeurs des champs ACF soient bien copiées ou traduites dans les versions en autres langues ? Toute aide ou documentation complémentaire serait grandement appréciée.
March 11, 2025 at 2:38 pm #16802285
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Hello, thanks for contacting us. Since this is an English support forum, I will reply in English. 1) Once you have set ACF field groups to Same fields in all languages, you should not be doing anymore changes to custom fields from WPML > Settings, that could create issue. Once you have set mode, WPML will set correct translation settings for all, so please revert back chnages done manually, if possible. 2) How did you translate the pages? 3) Please edit your 2nd langauge page and in backed check if the transalted content shows there fine in ACF fields, if yes, it could be that only issue is happening on frontend. Let me know and I will suggest next steps. Thanks, Drazen
March 11, 2025 at 5:34 pm #16803236
sandraB-42	Hello, Thank you for your response. I’m facing an issue where WPML translates the slugs for dynamic data, causing problems on the frontend. The builder doesn’t recognize the translated slug, which results in the fields not displaying correctly. However, when I revert to the original slug, the fields work as expected. I would like to prevent WPML from translating these slugs. Additionally, I’m experiencing an issue with ACF repeater fields. None of the repeater fields display data in the translated versions of my pages. Could you please assist me in resolving these issues?
March 12, 2025 at 7:45 am #16805313
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Hello, 1) This could be since you are using heading widget, and those are translatable, please try to add your ACF shortcode to Shortcode / code / widget and then re-transalte, WPML should not translate them then. 2) As for repater, does the content show in the back in ACF fields if you edit the page in WP editor, not bricks? Let me know. Regards, Drazen
March 12, 2025 at 9:49 am #16805999
sandraB-42	Hello, I am experiencing several issues on my site with WPML integration. Please note that I am not using any widgets in my configuration. ACF License Expired: My Advanced Custom Fields (ACF) license key has expired. Could this affect WPML’s handling of field translations or syncing of dynamic data? ACF Options Page Repeater Fields Not Displaying: I have an ACF Options Page that is set as translatable. However, the repeater fields on this page are not displaying any data in the translated versions, while they work fine in the primary language. Dynamic Slug Translation Issue: Despite having disabled slug translation in WPML settings (I have unchecked any option that would translate slugs), it appears that WPML is still translating dynamic field slugs. This causes the builder or code to fail to recognize the correct field names, resulting in data not being displayed in the translated pages. Could you please advise on: Whether an expired ACF license might cause translation or syncing issues, How to ensure that the repeater fields on the Options Page display correctly in all languages, and How to prevent WPML from translating dynamic field slugs so that the builder or code recognizes the correct field names. Thank you for your assistance. New threads created by Dražen and linked to this one are listed below: https://wpml.org/forums/topic/split-acf-options-page-repeater/
March 12, 2025 at 9:57 am #16806087
Dražen Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+02:00)	Hello, it would be best if we can stick to the topic of the ticket, to keep things clear, then if you have any other issue / doubts we can open new ticket for it. 1) I am not sure, but I assume you need to have a valid licence for ACF PRO, to use it. 2) ACF Options page, I have opened a new ticket: - https://wpml.org/forums/topic/split-acf-options-page-repeater/ 3) That option is not related to this, slugs are page slug (URLS) and that option is not related to shortcodes you are using. What you are doing is adding ACF shortcode to builder (these are not slugs) and you are adding this to heading title widget, which is then translatable. As said try adding shortcodes to proper widget, I think Bricks has shortcode widget, where you can add those and which should be used for this case. Regards, Drazen