Problem: The client was experiencing an issue where parts of a page were not translated, even after translating them in String Translation, as they still appeared in the default language. Solution: We resolved the issue by taking the following steps: 1. We created a
404.php
file in the child theme. 2. We made slight changes to the code. 3. We deleted the
wpml_st_upgrade_in_progress
key from the
wp_options
table. 4. We translated the strings again.
We then asked the client to check if the translated strings were displaying correctly.
Please note that this solution might be irrelevant due to it being outdated or not applicable to your case. If you're still facing issues, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket with us.
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.
