Home›Support›English Support›[Resolved] Change the field group translation setting result duplicate fields
[Resolved] Change the field group translation setting result duplicate fields
This thread is resolved. Here is a description of the problem and solution.
Problem:
Hi there!
When i updated ACF multilingual i saw the message:
"Change the field group translation setting
You can translate field labels and labels for Choices using String Translation. To do this, set the field group post type to Not Translatable."
I set field group post type to Not Translatable and now i see duplicated ACF blocks, take a look at the screenshots
Can i delete those duplicated ACF fields some how? As i can understand they are duplicated because of that settings? Do i need use older version of ACF Multiliongual?
Let me know if you need more information to understand why is this happening
Solution:
The manipulation is rather easier it consists of these steps:
1. Make the field groups translatable again.
2. Delete the field groups from the secondary languages.
3. Make the field groups untranslatable again.
4. Translate the field groups strings in String Translation.
I'll try to help you through all of them. 1. First step: Make the field groups translatable. Go to WPML->Settings. Then scroll down to the "Post Types Translation" section, and make it translatable check this screenshot https://i.imgur.com/9ddlHgc.png 2. Second step: Delete the field groups from the secondary language. You can follow the steps 3 to 6 in the "Making the Field Group Custom Post Type Not Translatable" section of this article https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/expert-translation-option/#using-expert-on-existing-sites 3. Third step: Make the field groups untranslatable again. That's the 7th step of the same section/article. 4. Fourth step: Translate the field groups strings in String Translation. Go to WPML->String Translation. You can filter by the field group, and translate the strings.
When i updated ACF multilingual i saw the message:
"Change the field group translation setting
You can translate field labels and labels for Choices using String Translation. To do this, set the field group post type to Not Translatable."
I set field group post type to Not Translatable and now i see duplicated ACF blocks, take a look at the screenshots
Can i delete those duplicated ACF fields some how? As i can understand they are duplicated because of that settings? Do i need use older version of ACF Multiliongual?
Let me know if you need more information to understand why is this happening
Hello and welcome to the WPML support forum. This is Jamal from the compatibility team behind this lust ACFML update.
I hope you did a backup before the update! If not, please make a full website backup and follow these steps:
1. Make the ACF field groups translatable again in WPML->Settings->Post Types translation.
2. Go to Custom fields->All custom fields. And for each secondary language, delete all the field groups.
3. Make the ACF field groups untranslatable again in WPML->Settings->Post Types translation.
If this does not help, please allow me temporary access to your website to check this further. Your next reply will be private to let you share credentials safely.
If you can provide a staging site with a state before the update, or a backup that you have made before the update, it will help us a lot trace the origin of this issue.
there so much info on this page... and all is mixed up... Expert options... Set translatable in 2 places... i just lost and confused...
So what is exactly for the "Advanced Custom Fields Multilingual (ACFML)" only to translate the fields of ACF?
If i need to translate only values can i just disable this plugin?
Can i just disable and not use this plugin? So it will works just like before?
Or can i just recreate those fields using same meta_key (and delete old one) with new ACFML plugin to prevent duplication on screen options? There is not so many...
*I believe when i delete some group the values and metas of this group will not be deleted
The manipulation is rather easier it consists of these steps:
1. Make the field groups translatable again.
2. Delete the field groups from the secondary languages.
3. Make the field groups untranslatable again.
4. Translate the field groups strings in String Translation.
I'll try to help you through all of them.
<b>1. First step:</b> Make the field groups translatable. Go to WPML->Settings. Then scroll down to the "Post Types Translation" section, and make it translatable check this screenshot hidden link
<b>2. Second step: </b> Delete the field groups from the secondary language. You can follow the steps 3 to 6 in the "Making the Field Group Custom Post Type Not Translatable" section of this article https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/expert-translation-option/#using-expert-on-existing-sites
<b>3. Third step:</b> Make the field groups untranslatable again. That's the 7th step of the same section/article.
<b>4. Fourth step:</b> Translate the field groups strings in String Translation. Go to WPML->String Translation. You can filter by the field group, and translate the strings.
4. Translate the field groups strings in String Translation.
I dont wont to translate field groups... i just wont to translate the values of created fields... i dont care if the field group will be in english when i will translate other languages.