Home›Support›English Support›[Waiting for user confirmation] I need to hide product attributes and their values from WPML Advanced Translation Editor when creati...
[Waiting for user confirmation] I need to hide product attributes and their values from WPML Advanced Translation Editor when creati...
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 want to hide custom product attributes and their values from WPML Advanced Translation Editor (ATE) when translating a WooCommerce product. Currently, all attributes are included in the translation editor, but I would like to exclude those values.
Symptoms:
No clear setting to exclude attributes from WPML ATE, and they continue to be included in the translation process.
Questions:
How can I hide custom product attributes and their values from WPML Advanced Translation Editor?
Is there an option or method to prevent attributes from appearing in the translation editor?
Thanks for contacting WPML forums support. I'll be glad to help you today.
1) Please go to WPML-> Settings-> Translation Editor-> Taxonomy visibility in the translation editor and select the "Only show taxonomy terms that haven't been translated yet" option, then click "Save".
2) Could you please share your Debug information with me?
You can read a detailed explanation about it here. (http://wpml.org/faq/provide-debug-information-faster-support)
The debug info will give me much information about how your site is configured.
I have already selected the "Only show taxonomy terms that haven't been translated yet" option in the WPML settings. However, the attributes are still visible in the Translation Editor, regardless of whether they have been translated or not.
My goal is to completely hide all attribute information in the Translation Editor and instead translate product attributes and variations using code when product information changes. Additionally, I need to display attributes and variations that require translation on a separate page, rather than in the Translation Editor on the product translation creation page.
1) Thanks for your reply. The attributes will appear in the translation editor if they are not translated.
2) You can translate the attributes by going to WooCommerce-> WooCommerce Multilingual-> Attributes tab.
3) The variation strings are translated in the translation editor.
4) If the attribute is created inside the product's edit screen, it will appear in the translation editor as it can't be translated via WooCommerce-> WooCommerce Multilingual-> Attributes tab.
The attributes are not showing in the WooCommerce Multilingual section. Could the reason be that I created custom attributes using code instead of global attributes?
If I create them as global attributes but do not translate them, will they be hidden from the translation editor?
After creating the attributes using Global attributes, If you don't want to translate them, please go to WPML-> Settings-> Taxonomy Translation section and set them as "Not Translatable".
If you want to translate them without using the translation editor, please go to WooCommerce-> WooCommerce Multilingual-> Attributes tab and translate the attributes before translating the products.
WPML doesn't provide a solution like that by default. There is an option to automatically translate all the terms at once using the translation editor. Kindly check this guide.
Is it possible to automatically translate attribute values and variations for each product when a new variation is added to the default language, but not the terms? If it is possible, can you share the documentation for that?
My advanced translator editor is getting stuck, and I can't click the save button if I don't add the translations in order. It also gets stuck if I make changes to HTML attributes containing a paragraph.
New threads created by Osama Mersal and linked to this one are listed below:
We try to keep one issue per ticket in our forum. Continuing with one ticket per issue helps supporters focus on one issue at once and enables other users to find solutions to their questions faster.
Therefore, I've split the other issue and created a new ticket with this issue.
