ACF fields translated through the advanced translation editor not showing up

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 contains 2 replies, has 2 voices.

Last updated by Alejandro 1 year, 2 months ago.

Author	Posts
April 18, 2024 at 2:11 pm #15539447
sophiaB-2	Tell us what you are trying to do? Translate a page Is there any documentation that you are following? https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/ https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/setting-the-translation-preferences-for-acf-fields-created-using-php-code/ Is there a similar example that we can see? What is the link to your site? hidden link
April 18, 2024 at 3:01 pm #15539840
sophiaB-2	I've included some images of the completed translation and then the English page and the empty German page for comparison. My site is password protected, but I can give you access in a private reply.
April 19, 2024 at 5:37 am #15541736
Alejandro WPML Supporter since 02/2018 Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00)	Hello, I'll help you get started while a supporter takes your case. 1) Could you please let me know what's the translation preference for those ACF Field groups? Since they are being use with a translation editor, then I'd suggest you use "sane fields across translations". 2) Also, can you let us know what type of fields are we talking here and how they are being displayed on the front end? (Via a page builder, plain pho code, etc). 3) You're not meeting our minimum requirements. Please read this guide to know what you can do about it: https://wpml.org/faq/checklist-before-opening-a-ticket-in-wpml-support/#how-can-i-increase-my-sites-memory-limit Let us know so we can understand what to do next.
April 19, 2024 at 7:43 am #15542136
sophiaB-2	I believe I have this resolved, though we are in development so I haven't had a chance to test translations on all content types/templates. If I run into additional issues, I'll submit a new request. These are flexible content fields created using ACF written in PHP using the acf_add_local_field_group function. I found the known issue post here: https://wpml.org/errata/advanced-custom-fields-local-fields-translation-preference-issue-for-php-registered-system-fields/ but the only workaround listed was using JSON, which isn't an option for me. Instead I found the workaround suggested in this support request: https://wpml.org/forums/topic/repeaters-flexible-content-generated-with-acf_add_local_field-and-wpml/ It would have saved me a lot of time and maybe would avoid some support requests being started if you include this workaround on the known issues page. I haven't had any memory issues, but I'll up my memory limit (we are in development so just on a staging site for now).