[Closed] Translations reverting to default language on the front-end

Hello,

Welcome to the WPML support forum. When it comes to ACF fields, setting up translation preferences for each field can be tricky. So, let's start by reviewing your configuration:
1. In "WPML > Settings > Post Types Translation" the translation preference for "Field Groups (acf-field-group)" should be "Not translatable".
Ref: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#translating-field-groups

2. Translation preferences for each field.
Depending on the method used to translate your pages, you will need to set different translation preferences.
- Go to "ACF > Field Groups" and edit your group. We have 3 different multilingual setup:
> Same fields accros languages: That's will be the setting to use in most cases
> Different fields accros languages: Use this one only if you use the WordPress editor to translate your pages and/or want totally different fields
> Expert: this mode will allow you to edit the translation preferences of all your fields manually
Be careful with this mode because some special fields such as "Repeater" or "Flexible content" need to be set with specific preferences. Read our documentation: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/

My recommandation is to start with "Same fields accros languages" and, if needed, switch to "Expert" to fine tune some translation preferences.

3. So now, let try to review your workflow
- Do you always use ATE to translate and edit your translation. If yes, then "Same fields accros languages" should be used.
- Then, make a small edit in the original page (add a space at the end of your title or a paragraph and save the page). That should be enough to trigger an update on the translation. Open the translation and re-validate it.

Does it solves the issue?

Hello,

Thanks for all the details. I needed to know some of them before being able to recommend you a workflow.

If you don't use ATE but the WordPress editor, then the recommandations for the translation preferences are totally different.
From the documentation I shared before you should use the "different fields accros languages" column as reference. Basically most of the fields should be set as "Copy once".

Let me explain a few important things:
1. When you are using the WordPress editor to translate your page, ATE should be deactivated.
See our documentation "translate manually": https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/

2. It's not recommended to switch editors because you could lose some translations.
If you translate a page using ATE, then switch to the WordPress editor and make changes. Next time you will save your original page, the translation that is still in ATE will overwrite your changes. That's why ATE should be deactivated in point #1

3. As for ACF fields, depending on the translation preferences, not all fields will be able in ATE, for example a field set as "Copy" won't appear because ATE will automatically copy it and you can't change the value in the translation. Same logic if you work with the WordPress editor, copied fields will be locked, you will be able to see them you you won't be able to modify their value.

I insist on those points because there is something that is still confusing to me. You say in your last answer "We don't use ATE" but point #2 of your previous message was "Some fields become unavailable in the ATE editor". That's why I'm not sure to understand your workflow.

Maybe you could provide me with a temporary admin access (wp-admin and FTP) – so I can have a look?

I will activate a private field for your next answer where you can provide that information safely (this field is only visible by you and the support team). Don't share your own admin account, create a new one that you will delete when we finish troubleshooting.

IMPORTANT: Before we proceed, please backup your site and database.

- Please in this private answer share the name of the group field used and the URL of a page that uses those fields where I can see the issue.