Background of the issue:
I am trying to translate all pages and products on my website. The issue can be seen on this page: hidden link.
Symptoms:
I expected everything in the details to be translated into the chosen language, but instead, I got many mixed languages, with content being half-Bulgarian and half-English. Screenshot: hidden link.
Questions:
Why are the translations not fully applied, resulting in mixed languages?
How can I ensure all content is translated into the chosen language?
I suspect that a temp user named temp-login-iE8OZ4h2ek75ACG is causing problems with finishing translations in the Advanced Translation Editor. This is because this kind of user (temp user) does not have an email address associated with it. Please see the attached screenshot. I suspect this because, in the Advanced Translation Editor Error Logs screen, I receive a message stating, "Active record record invalid: Validation failed: Email can't be blank." You can see it here: hidden link.
Do you allow me to delete this user so I can continue to investigate this issue?
Thanks. I deleted this user. It helped to solve the problem with the error I mentioned in my previous reply. And also helped to get on with investigating this issue.
I corrected this problem on your site for the product you provided as an example: hidden link.
Please see my explanations in a video I recorded for you: hidden link
Please watch my video to learn how to correct this issue, as well as for other products where it may occur.
The important thing to note is the difference between global and local attributes. You can read about taxonomies translations in the following guides.
I'm sorry for this mistake. I pasted the link to the product instead of the video link. I corrected it now in my previous reply. And I'm also adding the link here: hidden link
Hello, thanks for the video and support.
The most important is that I created the global attributes with the same name 2-3 days ago trying to resolve the problem, but the problem persist, so even if you delete the global attr. everything will still the same. I need a solution where I can translate everything for short time, can't do it one by one. How can I do that? As I said ignore the global attributes, I just tried to resolve the problem myself, but didn't work
I noticed that most of the gaps in the translations are in English only. And you suggest me to edit them one by one, which will take probably a week. We paid a lot of money to translate everything in the 3 languages, but now the custom or local attributes are skipped from the plugin mostly in the English version. I believe you should do something or compensate us for the inconvenience
Could you please send me a link to another product in English where this issue currently occurs, and I'll consult with our second-tier supporters about your case?
Please note that my weekend is Friday to Saturday, and I'll be able to continue checking this issue and helping you on Sunday.
Our second-tier supporter suggests trying the following.
1. Go to WPML -> Settings -> Post Types Translation.
2. Look for 'Products (product)'.
3. Change it to 'Translatable - only show translated items'. Please see the attached screenshot.
4. Click the Save button.
Check if it helps with this problem.
Can you please try it and let us know how it goes?
In addition to the above, our second-tier supporter suggests checking if the product attribute meta key is set to Copy in the database of your site. If you would like our second-tier supporter to check it for you, we require your permission to install a plugin such as WP phpMyAdmin or the hidden link">Adminer script. For Adminer, we need FTP access. Please let us know if you agree. I'm enabling a private message for the following reply. Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
