Skip Navigation

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 1 reply, has 2 voices.

Last updated by Andreas W. 11 months, 4 weeks ago.

Assisted by: Andreas W..

Author Posts
March 6, 2024 at 8:54 am #15377921

sebastianK-50

Hi,

this is a continuation of the following Ticket: https://wpml.org/forums/topic/acf-fields-are-shown-in-all-languages-and-acf-fields-dont-save-because-of-it/

We can select the fields on the pages again.
Something else I noticed now is that all ACF fields are shown in both languages in the ACF backend. Is that a bug or normal WPML behavior?
I remember it didn't used to look like this.

March 6, 2024 at 11:08 am #15378611

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

It is expected to see the ACF Field on the backend in both languages.

Take note, that I took a look into your old ticket, and it seems to me that you have set the "Field Group" Type in WPML >Settings > Custom Post Type Translation to "Translatable - only show translated content".

Please do set the "ACF Field Groups" inside the WPML settings to "Not translatable" and remove any earlier duplicated or translated groups from ACF, as you will run into unexpected issues when setting the Field Groups to translatable.

Un order to translate the fields, please follow this guide:
https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/

Best regards
Andreas

The topic ‘[Closed] all ACF fields in the backend in both languages’ is closed to new replies.