ACF flexible content field isn't synced

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

Problem:
The client reported an issue where the Advanced Custom Fields (ACF) flexible content field wasn't syncing with translations after adding a new flexible item. The translations were dropped because the keys weren't synced. The client also inquired about the checkbox option 'Keep repeater and flexible sub-fields in the same order as the default language' and whether it should be checked or unchecked.
Solution:
We advised the client to ensure that the ACF flexible field is set to COPY, not Copy-once, according to our documentation. We provided a link to the relevant documentation:
https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/
We also suggested that the client:
1. Change the ACF flexible field setting to COPY.
2. Check if the issue persists on a new page.
3. Provide WPML debug information as described in our documentation:
https://wpml.org/faq/provide-debug-information-faster-support/

If the solution provided here is not relevant to your case, either because it's outdated or not applicable, 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 the issue persists, please open a new support ticket with us.

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: Bug

This topic contains 7 replies, has 3 voices.

Last updated by Dražen Duvnjak 9 months ago.

Assisted by: Dražen Duvnjak.

Author	Posts
February 1, 2024 at 11:57 am #15254717
luminati-network-ltd.L	ACF flexible content field isn't synced with translations after add new flexible item. all the translations are dropped because keys wasn't synced
February 1, 2024 at 2:01 pm #15255268
Bruno Kos Supporter Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00)	Can you record us a video using tool such as hidden link to show the issue?
February 1, 2024 at 4:59 pm #15256112
luminati-network-ltd.L	Hi, I record a video: hidden link + I upload image that show that the translation of content_5 move to content_6 (because add new item) but the translation still on content_5 (now its different field)
February 2, 2024 at 9:02 am #15258211
Dražen Duvnjak Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+01:00)	Hello, thanks for the video, I understand the issue clearly. 1) I noticed you said that flexible field is Copy-once, please note that is not correct. It should be set to COPY as per our next docs, please check: - https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/ Can you please try to change it to COPY and check if the issue still happens? 2) Also please check if the issue still happens on the new page if you create one. 3) Please provide WPML debug as described: - https://wpml.org/faq/provide-debug-information-faster-support/ Regards, Drazen
February 4, 2024 at 2:00 pm #15263571
luminati-network-ltd.L	seems like its OK now when I update with new section on default lang it doesn't show up on translation and translations seems OK (without the untranslated section) what about the sync checkbox called: "Keep repeater and flexible sub-fields in the same order as the default language.". should I check or uncheck that checkbox?
February 5, 2024 at 7:53 am #15264401
Dražen Duvnjak Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+01:00)	Hello, great, glad to hear that. If you want to keep the same order and number of ACF fields then the checkbox should be checked. Regards, Drazen
February 7, 2024 at 2:08 pm #15277008
luminati-network-ltd.L	I face new issue that related to that issue. checkbox for sync is checked: "Keep repeater and flexible sub-fields in the same order as the default language." - I remove one flexible item from the middle of the page (it was 5) - the section that was number 6, become 5. - They share the same field names. - fields that was exist on the deleted flexible item (layout) but not exist on the next section (layout) now display on the layout. why? because contents_5_title was exist and not "override" with new field (it is empty) so now on translations it show the old values and not empty values like english because in english there is no field. that field is not exist on wpml translation editor. What can I do with that case? New threads created by Dražen Duvnjak and linked to this one are listed below: https://wpml.org/forums/topic/split-fields-that-not-exist-on-the-next-section-layout-now-display-on-the-layout/
February 8, 2024 at 8:06 am #15279956
Dražen Duvnjak Supporter Languages: English (English ) Timezone: Europe/Zagreb (GMT+01:00)	Hello, We limit 1 issue per 1 ticket, to keep things clear and easy to follow. I have opened a new ticket for your new issue: - https://wpml.org/forums/topic/split-fields-that-not-exist-on-the-next-section-layout-now-display-on-the-layout/ Since the original issue of this ticket is resolved I advise closing this one and continue our conversation in the new ticket. Regards, Drazen
February 11, 2024 at 3:29 pm #15290150
luminati-network-ltd.L	The ticket is "solved" but cause different issue. the bottom line is WPML and translations didn't worked correctly when acf flexible content should be synced 100% on delete/update/create add new field after page exist with translations

luminati-network-ltd.L confirmed that the issue was resolved on 2024-02-11 15:29:49.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.