I am trying to update some ACF fields content that are set to translate. The fields appear to be locked, however, I have the preferences set to translate for each of the fields. When I manually edit the translation for the page and then click update, the translations are reverted back to English and the field preferences are reverted back to copy.
Is there any documentation that you are following?
There is no documentations I am following. I have updated my plugins to the latest versions and bumped up my site memory to 128M.
I understand the issue you're having and will try my best to assist you in this matter.
The ACF fields will only appear locked if the Translation preference is set to 'Copy'. Upon reviewing the WPML Debug Info, I observed that the translation preferences for many fields are set to 'Not Translatable' or 'Copy'. Could you please check the ACF Field Group and ensure that the 'Translate' preference is selected for the fields you wish to translate?
If the preference is not selected there, please follow the steps below and hopefully, it will help.
- Navigate to "ACF → Field Group" and open the Field group which includes the specific field.
- At the top, there is an option to modify the Translation mode. Click on the "Change Option" link there.
- Choose the "Expert" mode from the available options.
- After selecting "Expert" mode, scroll down to the field you wish to change the translation settings for.
- Adjust the translation Preference and save your changes.
If the fields are cloned, ensure that you adjust the translation preference for the fields within the field group from which you've cloned.
If the issue persists, kindly share the name of the field where you're having the issue.
Please let me know the update. I will be happy to help if you need further assistance in this matter.
The Translation Options for my Field Group has been set to Expert and I have control over changing each of the fields to translate.
In my Page Builder group, I have a flexible content field named Page Builder which is set to Copy Once.
Within that, I have a variety of content types, but I will start with one name Hero. Within there, there are three fields that should be translateable: Content, Title and Button.
When I go and edit my Page that has the Page Builder added to it, the preferences for the translations for fields seem to get overwritten. You can see that they are then set to Copy and not Translate, even though that is the preferences for those fields.
The Hero element is the first item added in the page builder, so it should be the page_builder_0 items in the the Multilingual Content Setup on the page.
Any ideas why my translation preferences are not being carried over to the pages?
Hello There,
Thank you for providing such a comprehensive update.
It seems a closer inspection will be required to understand the root cause of the issue.
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to have a testing site where the issue is replicated.
You will find the needed fields below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
IMPORTANT
-Please backup site files and database before providing us access.
-If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Thanks for all of the assistance with this. I dug a little deeper and did some file comparison between our two environments and noticed that our production environment had been included a ACF configuration file which was the cause for the preferences to get updated. As soon as that file was no longer included, everything was working as expected.
