Home›Support›English Support›[Resolved] Split: translated products (imported as xliff translations) - do not show any product variations
[Resolved] Split: translated products (imported as xliff translations) - do not show any product variations
This thread is resolved. Here is a description of the problem and solution.
Problem: The client reported an issue where translated products did not display any product variations. This problem arose after attempting to translate products using XLIFF files and synchronizing taxonomies, which also led to the disappearance of variations in the default language.
Solution: We advised the client to ensure that all global attributes are correctly translated, as missing translations in the secondary language can prevent variations from displaying correctly. The steps include: 1. Confirming that global attributes are used and translated. For guidance on translating global attributes, visit Translating Global Attributes. 2. Using the Advanced Translation Editor (ATE) to automatically translate attributes by assigning them to a test product and selecting automatic translation. This method is efficient as it does not incur charges for numerical values, only text. For more details, see How to Translate All Taxonomy Terms at Once and Advanced Translation Editor.
If the solution provided does not resolve the issue or seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket at WPML Support Forum.
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.
Hello, thank you for your response, I somehow resolved the mysterious product, which has url in wrong format (synchronized translation etc - just blindly trying some tools).
Now it looks ok, but I have another problem - all translated products (imported as xliff translations) - do not show any product variations. I tried it with PHP shortcode - hidden link
what should I try to activate variations in DE version? If you want admin access, just write.
I have translated all taxonomies Titles (names) - but not the individual values - I have several hundred atribute values, which are just numbers - I do not want to translate it so I set in settings, that it is "Not translatable" - but before I did it, some automatic translation was done.
Can it be the problem? I do not want to click several hundred time "Copy to all languages" 🙁
I understand, but actually they need to be translated and existing in 2nd language, otherwise it will not work correctly as there are no attributes in 2nd language.
As you noticed, you can use automatic translation and translate them all at once from some test product you create and add there all attributes.
you can assign them all to one product and in ATE editor choose to translate automatically. Since most of them are numbers and etc, you wont be charged for that only for text, like Pin on etc.
Please try to translate like that 1 test product in ATE editor and there you can see what text need to be translated, and you can easily add it manually, or click to translate automatically.
I added new product with all the attributes, but if I try to translate it - the xliff file is just 8kB and definitely does not contain the attributes names.
I tried to translate some taxonomies which were used for one product to test it. I clicked to synchronize taxonomies button, which is located just under the taxonomy translations table.
Now all my products in default language are without variations - could it be because I also translated main taxonomy name (change original language of the taxonomy term from EN to CZ because it was wrong) - could it be it, what caused the deletion of product variation in original language?
I just tested and it should be there, you can test with ATE editor first to see if it works. Image attached.
Make sure default language of attribute and your default language of product / website is the same.
As for why your default language variations disappear, I am not sure, I can not tell, usually WPML does not affect your default language, but if you have mixed default language of attributes and product. For example attributes does not exist in default language of product then this can happen.
Best would be if possible to have all content created in same default language, and translated in all languages, then it should be work fine.
In DE version you can see, there are some attributes missing, it will appear, if I translate them, but my goal is not to translate them...
I am afraid as said before in order for variations to work correctly in all languages you need to translate them, it will not work correctly otherwise and if you do not translate them. Unfortunately, there is no other way here, as it will cause issues, you need to have attributes created and translated in all languages for them to work correct with products in all languages.
But that is what I have done partially yesterday - I translated around 10% of attributes (it is really too much to be done) - when I synchronized it several times it resulted in missing variations.
Therefore I would like to, that you look at it if it is set correctly and test it on some product - I just did it again - translated just the attributes, that are relevant to the produkt: hidden link
then clicked on synchronize and then the Czech variations are gone...
I reverted the site backup so you can test it if you want to see it by yourself.
the password is still the same
I am not able to translate all just to get the same result in the end. 🙁 It is too much time (which I do not have) doing it manually one by one.
New threads created by Dražen and linked to this one are listed below:
I understand now, I checked but I am not sure why it happens, I suspect it could be because you have mix of attributes in different default languages, but I would need to check it further, so I will open a new ticket and let's continue there to keep things clear:
As for your current ticket and reported here issue, as mentioned solution is to make sure you have attributes translated, they can not be Not translatable.
