Background of the issue:
We have setup multiple ACF field groups using PHP code in the functions.php file. These are all working for our primary language, English. However, after adding the French version and translating the pages, the ACF field groups which contain groups or flexible_content are all empty. I have ensured that all fields in the code have the correct wpml_cf_preferences key set, text and textareas set to 2 and groups and flexible_content set to 3. I've also tried creating a new field group via the ACF plugin interface with the options 'Expert' and 'Same fields across languages' and neither work.
Symptoms:
The ACF field groups which contain groups or flexible_content are all empty in the translated French version.
Questions:
What am I doing wrong?
Are you able to go into our testing site and investigate please?
How can we ensure all the same fields are copied across when translating a page and have all field values translated automatically?
How can translators manually edit text if needed?
Is there specific documentation on making ACF fields registered via PHP code functional for WPML?
I understand that some ACF fields registered using PHP are not working properly. We are aware of an issue where these fields registered using PHP are, by default, set to 'Not Translatable'. Please refer to the Errata linked below:
If the issue described in the Errata resembles what you're experiencing, could you please try the suggested workaround and see if it resolves the problem?
We also have documentation on registering ACF fields using PHP, which I believe you have already reviewed. However, here is the documentation for your reference.
If the issue persists even after configuring everything correctly, kindly share the code you've used to programmatically registering the fields. I will check and advice on what to do next.
This issue also persists when registering the fields via the Custom Fields interface so the fact the fields are registered in PHP doesn't make a difference.
After doing some of my own research and looking at other support tickets, I believe there is a global issue relating to repeater and group fields in WPML which is being fixed in your next update release.
Hello There,
Thank you for trying out the suggestions.
There are some issues reported in our internal system, but they don't appear to be directly related to the problem you're encountering. You mentioned that the flexible fields are empty in translation, but I haven't come across any similar reports.
To determine if the issue you're having is specific to your site or a more widespread problem. Please try to replicate the issue in our sandbox environment. The autologin link to our sandbox is provided below.
- hidden link
The WPML plugin and its addons are pre-installed on the sandbox. Please complete any remaining setup steps. Then, install the ACF plugin plugin and try to recreate the same issue.
If you're able to recreate the issue on the sandbox site, let me know. I will review it and advise you on the next steps.
The primary goal of using the sandbox site is to isolate the issue in a minimal environment, eliminating any server or external factors that might be influencing the behavior on the main site.
Please let me know the update. I will be happy to help if you need further assistance in this matter.
The Sandbox includes only WPML and its add-ons. That's why, the ACF is not insstalled in the sandbox. In case of third-party pluginss, we always ask our clients to install them on the Sandbox and then proceed to replicate the issue.
However, I have already installed ACF PRO on the Sandbox. If any other plugins are required to replicate the issue, please feel free to install and activate them.
If you can recreate the issue, please share the steps on how I can check and trace it. I will review them and do my best to assist you in this matter.
I've managed to get it working on the staging site and also on our testing environment too. However, we are still having issues with strings not being copied over for fields containing nested groups / repeaters.
For example, we have a comparison chart field group which contains the following structure:
Header (Group) - 3
- Title - 2
- Lead - 2
(The above now works!... However the below doesn't...)
I’m glad to hear that you’ve successfully made the flexible and group fields work on the site.
Regarding the issue in nested fields - We’re aware of an issue with nested repeater fields where values aren’t copied over to the translation in the nested fields. Please check this errata for more details.
If the issue you’re experiencing on your site is the same as what’s mentioned in the Errata, your current field configuration shouldn’t be causing any problems. According to the workaround in the Errata, the translation preference for the parent field should be set to ‘Copy Once,’ and based on the configuration you’ve shared in the last message, the parent field settings appear to be correct.
However, if the subfield value isn’t getting copied over, it’s likely due to setting the translation preference of those sub-fields to ‘Translate’ (2). You can keep the settings for the parent fields (Repeater/Group) as ‘Copy-once’(3) and set the translation preference for the subfields (Text, Description, Name, etc.) to ‘Copy’ (1).
Once done, make a small change in the default page and then try to update the translation. The value should be copied over to the translated page.
Let me know how it goes. I will be happy to help if you need further assistance.
I've checked the errata and can confirm this is the issue I'm facing. The workaround mentions changing all repeater and nested fields to (Copy Once). I can try doing this, but won't this mean the strings won't be automatically translated?
The workaround you mentioned setting the sub fields to (Copy).. What the differences here? All I'm trying to do is is ensure all the fields are translated automatically.
Sorry, could clarify or provide an example please before I try implementing this.
Thank you for confirming that the issue you're having is the same as what is outlined in the Errata.
As you mentioned in your last message that you want to copy the field data to the translation, I recommended setting the translation preference for the field to 'Copy.' If you set the translation preference to 'Copy-once' by following the Errata, the field data will also be copied to the translation but for one time. In either case, the content will not be translated automatically.
If you want to translate the field data automatically, you can set the translation preference for the fields to 'Translate'(2) I can confirm that with this setting, the contents within the fields set to 'Translate' are translated automatically. You can also check in the sandbox I have shared.
If the field data is not being translated, please check the field settings again. If you are still programmatically registering the ACF fields, go to "ACF > Tools," enable "Scan local fields for changes to translation preferences," and save the changes.
Once done, clear the caches and open the default page. Make a small change to the page title. If automatic translation is enabled, wait for it to complete the translation update. Otherwise, manually update the translation and check if the field data is now showing in the editor.
Let me know if that helps or if you need further clarification or assistance. I will be happy to help.
Thanks for that.. I think I'm making some progress.
The ACF > Tools," enable "Scan local fields is good to know.. I'm surprised I haven't come across this anywhere in your documentation yet!
So the only fields where I'm struggling with now are the ones in the ACF custom options_page. I think it's because I originally had these set to copy once, when they should've been copy. Is there a way of clearing the translated versions of the custom ACF options pages and starting from fresh with these pages?
I'm glad to hear you're making progress! Since ACF option pages are not stored as traditional pages in the database, they can't be deleted through the WordPress interface. However, if you need assistance with deleting option pages, the ACF support team can help you better!
If you believe the translation preference for the fields in the option pages was incorrect, you can update the translation preferences for these fields and then translate the option page contents again. In that case, it is not required to delete the option pages. Alternatively, you can create a new options page, configure the translation preferences for the fields correctly, and then proceed to translate the field contents.
Regarding the issue with the Menu_item description field, if the translation preference for the field is set correctly and the field is added to a page or post, the field data should be translated when you translate the page or post. If this is not happening, please review the field configuration to ensure that the translation preference is set to 'Translate'. If the field is added to a WordPress menu, you can translate the field contents by going to WPML > String Translation.
However, if the suggestion above doesn't help in translating the field contents, please create a new ticket with as many details as possible. As we are allowed to discuss one issue per ticket, one of our support team members will take your ticket and assist you accordingly.
Let me know the update. I will be happy to help if you need further assistance.
Best regards,
Prosenjit
The topic ‘[Closed] ACF field groups not copying over flexible content and group fields’ is closed to new replies.
