Split: Cannot add translation to ACF button field label.

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

Problem:
The client is experiencing an issue where updating the default language page causes the pages in other languages to break. This seems to be due to the translation of ACF field group names, which should not be translated to maintain correct association with the templates.
Solution:
We recommend that the client ensures consistency in the translation method. If using the WPML Translation Editor, avoid manually editing the translated pages. Conversely, if preferring manual translations, switch to the WordPress Editor. This can be done by selecting the "WordPress Editor" option in the sidebar to prevent layout or configuration issues.

Please note that this solution might be outdated or not applicable to your case. If the issue persists, we encourage you to open a new support ticket. We also highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please contact us through the 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.

This topic is split from https://wpml.org/forums/topic/cannot-add-translation-to-acf-button-field-label/

Tagged: Documentation request

This topic contains 1 reply, has 2 voices.

Last updated by Lucas Vidal de Andrade 8 months, 1 week ago.

Assisted by: Lucas Vidal de Andrade.

Author	Posts
March 14, 2024 at 4:48 pm #15411585
emilM-2	Hello, Thank you for the feedback, the translate option of the ACF fields seems to work and the translations are displayed. But now there is another issue - when I update the default page other languages pages get broken. It seems that the ACF field group names somehow get translated. Is there any way to prevent them from translation, so they are associated correctly with the templates? Here is an attached example video of the problem. I've restored the database of the staging to working state, so you can try and replicate the issue. hidden link Thanks in advance!
March 14, 2024 at 5:45 pm #15411808
Lucas Vidal de Andrade Supporter Languages: English (English ) Spanish (Español ) German (Deutsch ) Portuguese (Brazil) (Português ) Timezone: America/Sao_Paulo (GMT-03:00)	I noticed that your pages are set to "WPML Translation Editor" (see image), but you are manually translating them. Please choose only one option. That means, if you choose to use WPML's translation editor, you shouldn't edit the translated pages directly. If you wish to do that, please change the option to "WordPress Editor", in the sidebar. That way, you are less likely to run into a layout or configuration issue.
March 15, 2024 at 9:39 am #15413619
emilM-2	Hello, Thank you for the advice, after updating the translations only with the WPML editor, the pages are working correctly! 🙂 Wish you all the best, and have a nice day!