That was actually the point of whole operation - is not to update the upsell and translations, but simply set the price and quantity, as well as the upsell to the main language, and the upsell was pulled from there and were not included in the translation.
Thanks for your update. Could you please answer the following questions to help me understand the issue better?
1) Did you update the main product's translation after adding the upsell products?
2) Are the upsell products translated?
3) Would it be possible to replicate the issue on a fresh sandbox site with WPML and WooCommerce plugins only?
1. yes, it main product was updated, but only prices and related (upsell) fields
2. Yes, upsell products are translated
3. You know, I guess we can, but seems like I did it ones for similar problem on this website.
products.xml → initial import
products for update.xml → file for experiment, you cant use it to update the products. Upsell products must be changed for product below 2 out of 4 must be removed after import in both EN and DE
hidden link hidden link
product
en hidden link
related are present
de hidden link
no related products present, but it must be controlled by initial product
I guess if I will click Update, they will appear in translated products as well (this is expected behavior right after the import)
Thanks for your update. I've updated all products in both languages. After that, I updated the mentioned product in English and translated it using the WPML Translation editor.
When checking the translated product, it works as expected. (hidden link)
Would you please check it and let me know if it works correctly?
Problem exists while there is no straightforward translation for the product details and the original product's info is used. For example: the price is always set for the main language only and it works well, but related products must always be set separately? Is it correct?
It's fine for related, not a big deal to make additional imports with product's SKUs. But if we're talking about dozens of attributes that are already translated as a taxonomy, will it work and update secondary languages without manual resaving them if I don’t want to import them separately to every lang? Too much additional job needed to prepare import file with all attributes translated in it… Our strategy is to import main lang only as attributes are the same.
If you don't want to translate attributes, you can set them to not translatable and import them once, but I'm not sure if that would be the best approach.
If the attributes are already translated, they should work correctly without issues, and you can bulk update the products if needed.
