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
- 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 -
- 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 -

Supporter timezone: Europe/Vienna (GMT+02:00)

Tagged: 

This topic contains 4 replies, has 1 voice.

Last updated by Bigul 3 weeks ago.

Assisted by: Bigul.

Author Posts
February 26, 2025 at 9:32 am #16749966

matthiasR-28

Background of the issue:
I am trying to use ACF field groups with WPML to translate them to a second language. Initially, everything worked when I copied a field group to the second language. However, when I add new fields to the primary language after the initial copy, I can't copy these new fields to the second language, even with the 'Same fields in all languages' option enabled.

Symptoms:
New fields added to an ACF field group in the primary language are not being copied to the second language.

Questions:
Why are new fields not copying to the second language after the initial field group copy?
How can I ensure new fields are copied to all languages?

February 26, 2025 at 7:44 pm #16753250

Otto
Supporter

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

Timezone: America/Argentina/Buenos_Aires (GMT-03:00)

Thank you for contacting WPML support.
While you are waiting for one of my colleagues to take this ticket and work on it, let me provide you with the first debugging steps or if I can help with the issue quickly.

Please try this:
- Make a small change to a field that already appears in the translated group
- Go to the WPML → Translation Management screen, select the ACF field group, and send it to translation again

Best Regards,
Otto

February 27, 2025 at 3:42 pm #16757032

matthiasR-28

Hi Otto, unfortunately this doesn't fix the issue.
When doing the changes and sending it to translations again, only the original fields show in the WPML translation screen. Due to this the new fields are still not coming along...

Can we try another way to fix this?

March 1, 2025 at 4:39 pm #16764174

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+02:00)

Hello,

Thank you for the updates. Please try the following steps after a full site backup {mandatory} and check if there is any difference in the result.

1) Upgrade to the latest version of WPML (4.7.1 series). May you have to visit Plugins>>Add New>>Commercial tab and click on the *Check for updates* button to get the WPML automatic upgrade links of the latest version. This step will help us refresh the installer caches.
2) Clear all types of caches
3) Update the post having the issue in original language (to refresh the translation settings)

--
Thanks!

Bigul

March 10, 2025 at 10:08 am #16795536

matthiasR-28

Hello, the issue is still there after doing the things above. Everything is updated, after the update i added a new field in the original language and saved it while the option 'same fields in every language' is selected, but without result.

March 10, 2025 at 3:37 pm #16797414

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+02:00)

Hello,

Thank you for the updates. A couple of requests for tracking the issue.

1) Please let us know the exact steps to reproduce the issue on your site. It will be great if you can share a couple of screenshots for a better understanding of the ACF Fields & its settings.

2) Please fill the private details fields after a full site backup. I would like to access the admin area of your site for further checking. Refer to the following links for more details about our private information sharing policies.

https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/

hidden link

--
Thanks!

Bigul

March 11, 2025 at 4:28 pm #16802866

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+02:00)

Hello,

Thank you for the details and login information. Normally we don't have to translate the ACF Field Groups to a secondary language (in your case French). We officially recommend setting it as not translatable. Becuase we can translate the ACF field values and options using WPML Editors (Advanced or Classic).

Please check the attached images and the following documentations for more details and let us know your feedback.

https://wpml.org/errata/advanced-custom-fields-field-group-should-be-set-as-not-translatable/

https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/

So please check you are getting the expected result for ACF Fields in Winkels' posts (in Dutch and French).

--
Thanks!

Bigul

2025-03-11_21h54_07.png
2025-03-11_21h52_50.png
March 12, 2025 at 9:09 am #16805828

matthiasR-28

Thanks for looking into it, but this shouldn't be the way to solve it, right? We need to have the same fields in each field group, in both language. We want to be able to edit the values of the field groups in the WordPress editor, which isn't possible without having the fields in the field group. The first time, it worked to copy the fields from the original language to the field group in the second language—why is this no longer possible?

March 12, 2025 at 11:43 am #16806790

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+02:00)

Hello,

Thank you for the updates. Hope you are translating the posts manually from the WordPress Editor - https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/

Normally the fields will be synced to secondary languages. So please make sure the translation is complete (pencil icon), then update the original language post and make sure you are getting the expected results or not.

If the problem remains, please share the names of the fields you are having issues with.

--
Thanks!

Bigul

March 13, 2025 at 9:29 am #16810758

matthiasR-28

Hey, we tried this multiple times but without succes. There are multiple fields in multiple field groups that we have this problem with but an example are the 12 last field (see screenshot) in the dutch version of the fieldgroup 'CPT-Store'.

Schermafbeelding 2025-03-13 om 10.28.46.png
March 13, 2025 at 4:24 pm #16812921

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+02:00)

Hello,

Thank you for the updates. Please try the following steps after a full site backup {mandatory} and make sure the issue exists or not.

1) Visit WPML>>Settings>>Custom Post Types Translation
2) Choose *Not Translate* option for ACF Field Groups (acf-field-group)
3) Save the changes
4) Visit ACF>>Field Groups
5) Delete 'CPT-Store' Group's French Translation (also from the trash)
6) Update a Winkels' Post having the issue in original language
7) Then update the translation of Winkels' post
8) Also check, it works as expected for a new Winkels' post

--
Thanks!

Bigul

March 18, 2025 at 12:37 pm #16830123

matthiasR-28

Hello, sorry but this is not an option. This would mean that every time i add a new field in the original language i will need to delete my translated ACF fields and regenerate them again. This is not ideal.

We just want to have the newly made ACF field go along in the other language automatically, without deleting anything. We can't afford to translate everything again.

It worked in the past, it should work now also.

March 18, 2025 at 4:22 pm #16831442

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+02:00)

Hello,

Thank you for the updates. Does it happens after upgrading to the latest version of WPML?

It will be great if you can share a screecast (screencapture) of the steps you are following to reproduce the issue. It will help us a lot in our internal discussion. You can share it via Google Drive.

--
Thanks!

Bigul

The topic ‘[Closed] Adding fields afterwards in an ACF field group is not coming along in the other languages.’ is closed to new replies.