[Resolved] Translating Woocommerce attribute with new dashboard
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is unable to translate WooCommerce attributes using the new translation manager in WPML despite following the correct steps. Solution: If you're experiencing this issue, we recommend checking if the translation is set as a "Duplicate" of the original product. Duplicates are linked to the original and update automatically with changes to the original, which might prevent independent translations. To resolve this, open the translated product in the WordPress Editor and click "Translate independently" in the right sidebar. Additionally, ensure that the translation method for the product is set appropriately in the WordPress Editor. You can choose between "WPML Translation Editor" and "WordPress Editor". We suggest using the WPML Translation Editor for translating products.
This solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I'm trying to use the new translation manager in WPML for my WooCommerce site at hidden link.
Symptoms:
The attribute in WooCommerce won't translate despite following the steps correctly.
Questions:
Why won't the WooCommerce attribute translate using the new translation manager?
What steps should I follow to ensure WooCommerce attributes are translated correctly?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
Generally, each attribute should be translated together with the product that they are assigned to. Did you already try to edit the original product, save it again, and then translate it?
Further, global attributes that are created at Products > Attributes are translated at WPML > Taxonomy Translation.
You can further sync those global attributes at WooCommerce > WooCommerce Multilingual > Status > Troubleshooting.
If this will not solve the issue, please let me know.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Did you verify that the attributes are set to "Translatable" at WPML > Settings > Taxonomy Translation? Note, thus only matters for global attributes that were created a Products > Attributes.
Custom attributes, that are created directly on the original product can not be synced globally. They will only be translated, and then each product will be translated with the WPML Translation Editor. Using the WordPress-Editor for translation is not an option in this case.
Did you try to edit the original product, save it again, and then apply the translation using the WPML Translation Editor?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
I would like to request temporary access (wp-admin and FTP) to the website to investigate the issue further.
You can find the required fields below the comments section when you log in to leave the next reply. The information you provide is private, meaning only you and I can see and access it.
IMPORTANT
Please be sure to back up your website and database before granting us access.
If you can't see the "wp-admin / FTP" fields, your post and website credentials will be set to "PUBLIC." DO NOT publish the data unless you see the required wp-admin / FTP fields.
I may need to install a plugin called "All In One WP Migration" to create a copy of the website so I can investigate the issue further.
However, I would also be very grateful if you could provide a staging site or a copy of the website from your server for this purpose.
If you have any questions about creating such a staging site, you can consult your hosting provider. Please note that WPML must also be registered on this staging site at https://wpml.org/account/websites/.
If you are unable to provide such a copy of the website for testing, please let me know on this ticket.
The private reply form looks like this: hidden link
Click "I still need assistance" the next time you reply.
Video: hidden link
Please note that we are required to request this information individually on each ticket. We are not permitted to access any credentials that were not specifically submitted on this ticket using the private response form.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
What is kind of confusing here, is that on your example, the original product is English and the translation is Hebrew.
At the same time, the global attributes at Products > Attributes are created in Hebrew. Usually, it would be advisable to develop the products and their global attributes in the same source language and then translate them into a second language.
Also, if you revise Products > Attributes or WPML > Taxonomy Translation > sizes then you will see that there is a huge mix of attributes with different source languages and even various duplicates do exist.
I would suggest sorting out these attributes first, making sure each attribute exists only once.
Further, if the original global attributes are created in Hebrew, then I would suggest also creating the original products in Hebrew and then translating them to English.
Yeah, I know — my client is making a mess. It was my plan to fix it, but I wasn't sure if that was the problem.
I'll try to fix everything and see if it works. Thank you!
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Yes, in fact, I have a similar issue on another site right now.
It should be avoided to have any duplicated global attributes and the ideal workflow would be to use the same source language for products and global attributes.
Please give this a try and in case that this will not solve the issue, please let me know.
Hi again, I think I did everything right, did all the attributes in the original language and fixed everything, but the translations still not working as expected, the attributes is not translated to the second language (English).
please advice.
I need to send you new server details so please let me give you the details privately again 🙂
thanks
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Your example: hidden link
The original product is Hebrew.
The translation is a "Duplicate", which means that it is connected to the original product and will be overwritten each time you update the original product. See screenshot.
I would not suggest creating "Duplicates" and instead creating independent translations for your product.
To do this, open the translated product on the WordPress Editor and inside the right sidebar click "Translate independently".
Further, on the right sidebar of the WordPress Editor, while editing the original product, you will be able to select the translation method for the content.
You can choose:
"WPML Translation Editor" (currently set on this product)
or
"WordPress Editor".
I would suggest translating those products using the WPML Translation Editor.
Also, please take note that at WPML > Settings > Custom Term Meta Translation some fields were set to "Translate" but those fields did not require translation. You only need to set fields to "Translate" if you need their values to show up inside the WPML Translation Editor.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.