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.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
- | 9:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | - |
- | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | - |
Supporter timezone: Europe/Madrid (GMT+02:00)
Tagged: Known issue, WCML
Related documentation:
This topic contains 52 replies, has 0 voices.
Last updated by alirezaS-3 1 week, 3 days ago.
Assisted by: Marcel.
Author | Posts |
---|---|
June 18, 2025 at 5:23 am #17144527 | |
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
It might even be the example file that is triggering issues on my test running only with WooCommerce, as if I create a new variable product, export, and import it with WooCommerce only, it works. I then translated the product. Now, to run an export it seems like you to disable the patch plugin "wpmlimport-137" before running the export, then enable it before running the import. Anyhow, now the translated product is missing from the export file. I see quite a lot of unexpected behavior between all those tests and need more time to investigate. --- Take kindly note, that the next update for "WPML Export & Import" is currently in development and will solve the reported issue. |
June 19, 2025 at 1:04 am #17148448 | |
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
I now did the following: 1) Created a new variable product and translated it into all active languages This worked as expected. I can offer once more to take a closer look at this directly on your site, if you wish but as I mentioned earlier, you early example did not work, as you used for variations the value "id:26" in some rows, and this does not match the parents product's ID which in this case was "26". |
June 24, 2025 at 7:32 pm #17166573 | |
alirezaS-3 Site owner |
So you were not able to import the example csv file from your own website ? Can you show me the export file you exported ? It should then be possible for me to import this file to the test site. |
June 24, 2025 at 11:16 pm #17166921 | |
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
I have honestly not yet run further tests with the demo file on the second sandbox. I am not sure if the issue was with the demo import file or that our first sandbox was damaged. On the second sandbox, I created products, translated them, exported them, then deleted them and ran an import. On the sandbox, open the File Manager and go to /uploads/wc-imports One-Click-Login: |
July 1, 2025 at 3:31 pm #17189356 | |
alirezaS-3 Site owner |
The product you have on the test website has 'color' as the variant name in all three languages. It works if 'color' is spelled the same in all languages. It doesn't work if you use 'color', 'farbe' etc. |
July 2, 2025 at 7:04 am #17190960 | |
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
I translated the attribute labels and created a new export file. It looks like we are not exporting the translated attribute labels. I see that this is a feature that was not yet supported, and our developers are currently working on implementing this into the next update to WPML > Export & Import. I am following up with our compatilbity dev team about this and will get back to you once I receive their feedback. |
July 3, 2025 at 5:07 pm #17198972 | |
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
The export issues about untranslated attribute names on exported CSV files from WooCommerce have been escalated internally. Once I receive feedback on this matter, I will notify you on this ticket. |
July 4, 2025 at 11:20 am #17201329 | |
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
We found out that when exporting products, if the admin toolbar language selector is set to All Languages, it will export all products, and the Attribute name will indeed be in the default language. But if you use the language selector to specify a particular language, then the attribute name will be the name in that language. This means you would create one export file per language and then import all those files. First, enable WPML > Export & Import, then import the files, and finally merge the imports at WPML > Export & Import again. Please let us know if this works out for you. |
July 9, 2025 at 5:58 pm #17220644 | |
alirezaS-3 Site owner |
So where can I find your export file ? - i want to test this in your test environment. |
July 10, 2025 at 1:26 am #17221418 | |
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
I have not created one export file per language on my test. This proposal came from the second-tier support. Please follow the advice and give this a test. |
July 15, 2025 at 6:28 am #17236109 | |
alirezaS-3 Site owner |
We have always exported the products by first selecting the language in the admin toolbar, and thereby having two export files, one for EN and one for DE. I need to see a csv file from you where the attribute name 'color' is different for the two languages. The one you have which has the same value, ie. 'color', for all languages is no-go. Haven't you also reached the point where you can see that there's an issue/fault with your plugin ? |
July 15, 2025 at 7:47 am #17236519 | |
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
Yes, I was able to confirm an issue when exporting all languages into one file and reported this to the second-tier support with a site package. The second tier support tested the package and mentioned that if you use the language selector to specify a particular language, then the attribute name will be the name in that language. Since then, we have been waiting for confirmation if this workaround solved the issue on your site. Do I understand correctly that on your site, currently exporting one file per language does not solve the issue? If so, then please provide again admin access to the site, as I will need to run further tests. The private reply form is enabled. |
July 23, 2025 at 11:21 am #17263569 | |
alirezaS-3 Site owner |
I need to see a csv file from you where the attribute name 'color' is different for the two languages. The one you have which has the same value, ie. 'color', for all languages is no-go. |
July 25, 2025 at 3:11 pm #17271675 | |
Marcel Supporter
Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: Europe/Madrid (GMT+02:00) |
Hi, As my colleague Andreas is currently unavailable, I’ll be handling your ticket for now. You were discussing the export of products to CSV using the WP All Export Pro plugin. If from the export page "All languages" is set in the admin toolbar language selector then it is correct that for the attribute label column the label will be in the default language for all products (including translated products). But the workaround is to use the admin toolbar language selector and repeat the steps to export products in each language separately (so there will be one CSV for each language). In each CSV file the attribute label will be in the current language, not the default language, as required. Best regards, |
July 30, 2025 at 6:17 am #17280527 | |
alirezaS-3 Site owner |
Hi, If you read back you can se that I'm already exporting in separate languages. Let's focus on a simple csv file. Please provide a csv file where the attribute name 'color' is different in the two languages. The one you have which has the same value, ie. 'color', for all languages is no-go. Thanks. |