However, I still noticed a flaw on the French version. As you see, with some of the translated sizes, there is a space between the number and the cm part, while with other sizes, there's not. This looks very unprofessional. When I tried to fix it the last time by editing it in the ATE, all the sizes I had to edit got unmapped. I literally have no idea why the French translation is so inconsistent that it sometimes put those spaces and sometimes not... The English translation doesn't have that issue. Must be an issue with WPML I assume. Can you please fix that? I am not going to try myself because I already tried many times and each time the mapping gets lost.
Thanks it is fixed now, after all. However, I am concerned looking forward. I have thusfar only translated 11 of my 379 products. So if such problems keep arising than it wouldn't be worth it for me to keep using WPML because the amount of time it would cost to keep fixing these issues is gonna be ridiculous. Can you please tell me:
1: how to prevent the issue that there are less variants in the translated product than in the default language from happening (like we saw in both the dog face hoodie and the dog facce teddy lounge)?
2: How to prevent the issue with the translated variants not being mapped (which happened with the dog face teddy lounge because I had to rename certain sizes)?
3: How to prevent the issue with inconsistent translation (Like we saw with the sizes with the dog face teddy lounge)?
2) It would be helpful to translate the attributes in WooCommerce Multilingual-> Attributes tab, then translate the products.
-Problem is, I get my products from AliExpress and most often use the DSers plugin to import a product from AliExpress, and push it to my store. I noticed that for products which I have imported this way, the attributes don't show up in the WCML>attributes. On the platform of DSers I already set the sizes and colors. It seems like the only products of which the attributes show in WCML>attributes are the products that I actually created in WooCommerce, rather than in the DSers platform and then pushed to the Woocommerce store.
Also, the dog face teddy lounge was done via DSers. So maybe the fact that those sizes were not in WCML>attributes is what caused the variants to unmap after I edited them in the ATE?
3) This can be avoided by reviewing the translation before approving it to fix any issues with the translation before publishing the product.
-Well, what I actually wanted to ask is how to avoid the problem that WPML translates these sizes so inconsistent in the first place? It looks like maybe WPML uses a hybrid of translation tools which makes it so inconsistent?
Also, the way you prescribed (reviewing and if necessary, editing, before publishing) was what I had already been doing all this time and that didn't work.
1) Yes, that could be a cause of the issue because DSers is not officially compatible with WPML, so it's expected to face issues. Kindly check the compatibility list here. (https://wpml.org/plugin/)
2) It didn't work on some variants of the imported product, but you shouldn't face issues if it's a WooCommerce-created product.
Also, when I checked some other attributes in your default language, I found that they have spaces between numbers and cm, so if the imported product was imported like that and you sent it for translation, then edited it, that could be the cause of the issue.
"1) Yes, that could be a cause of the issue because DSers is not officially compatible with WPML, so it's expected to face issues. Kindly check the compatibility list here. "
-Ah okay, is there any way to work around it?
"Also, when I checked some other attributes in your default language, I found that they have spaces between numbers and cm, so if the imported product was imported like that and you sent it for translation, then edited it, that could be the cause of the issue."
-Where did you see that? The only place I saw that was at the size"30-35-cm borstomtrek" where there was a stripe after 35, but the inconsistencies were all over the product, not just at this size.
1) I'm afraid that there is no workaround available except fixing issue by issue like we handled this ticket, so if you face any other issues, please create a ticket for the issue, and we will do our best to help you fix it.
2) I saw the attributes I mentioned here. (hidden link)
2) I saw the attributes I mentioned here. (hidden link)'
But that's not on the dog face teddy lounge, so how is that relevant? (I will take care of that when I start translating those products, but I just don't see how this has any link with how it got translated at the dog face teddy lounge)
The real problem is that in the translation to French, the format is inconsistent, while on the Dutch problem the format is consistent.
I meant that if the default language product had this issue and you sent it to translation, then edited it to fix it. The translated product will have the same issue.
The automatic translation is a machine translation, so it's important to review it before approving and publishing the product.
In order to check if this issue is reproducible, please create a test product named WPML test and translate it to check the "cm" issue.
"3) This can be avoided by reviewing the translation before approving it to fix any issues with the translation before publishing the product."
Right now, the way I am translating is by going to WPML>translation manager>select product I want to translate>Then, on 2. Select translation options, I select Translate > Then at how do you want to translate, I pick Automatic translation (rather than manual translation), what happens then is a popup will appear which asks me to review the translation before publishing it. When I press on this, this will lead me to the translated product page, with a notice on top asking me where I accept the translation or if I want to edit first before publishing it. Could it be that the fact that the product is already sort of saved at the moment when I get to see the preview, and that it could be causing issues when I want to edit after this? If at 2. Select translation options, I select the translate myself option, the product will be pushed the the awaiting translations tab. If I to the awaiting translations tab, then press Translate on the product I want to translate, the ATE will open. I then can press the blue Translate automatically button, all the fields will get filled out. I can then check if all attributes are right and maybe edit them. If I do it this way, WPML wouldn't need to generate the product page before I make sure all attributes are right. So do you think that maybe this way, it can prevent the problem of variants not mapping after editing them? (because if I did the translate automatically at "2. Select translation options" there would be a preview product already before I even make sure all variants are right, so maybe that preview product would cause any problems in the cache?)
Also, I see you installed the Copy & Delete Posts plugin on my site. Can I deactivate and delete it?
1) The second approach could be more suitable for your issue. (Translating inside ATE) In order to be sure of that, please translate a product and test if you will face the same issue and let me know the result of this test.
2) I didn't install any plugins on your live site, so please feel free to deactivate and delete it. I installed on your staging site the duplicator plugin only.
