kisa
|
I just shared it with you on your email address, thank you!
|
Lauren
WPML Supporter since 10/2015
Languages:
English (English )
Timezone:
America/New_York (GMT-04:00)
|
I haven't forgotten about you! I'm having a hard time importing the file because it's so large, but hopefully the current attempt will complete and I can troubleshoot there on our Cloudways server. That way I can share access and we can both see what is happening, versus testing on a local server. Stay tuned... I hope to have more information for you shortly.
|
kisa
|
Hi,
Thanks for the update! I completely understand, feel free to reach out if you need anything from my side. I’ll stay tuned for any updates!
Looking forward to hearing from you soon,
|
Lauren
WPML Supporter since 10/2015
Languages:
English (English )
Timezone:
America/New_York (GMT-04:00)
|
Unfortunatley, I've not been able to set up a copy of the site, I think due to the file size. The Duplicator attempt failed, the All in One Migration failed, and Cloudways failed. Is it at all possible for your hosting provider to set one up for you so we can test minimal settings? Or have you tried anything like WP Staging or similar systems?
If not, is there a time when it would be convenient to put your site in maintenance mode so we can test? I understand that is not ideal, I'm just trying to brainstorm how we can troubleshoot and rule out any possible conflicts to try and determine where this issue is coming from.
|
kisa
|
Thank you for your message.
We’d really prefer not to put the site into maintenance mode, as it tends to be quite detrimental for us in terms of user experience and visibility. We're going to check with our hosting provider to see if it's possible for them to set up a staging site on their side that we could use for testing.
In the meantime, it would be great if you could try again on your end, just in case something goes through this time.
We also tried publishing another product today with around 11 different variations and unfortunately it still bugged in the english version translated with WPML. So we're definitely eager to get to the bottom of this.....
Thanks again for your support—please let us know if anything else comes to mind!
|
kisa
|
My host provider succeeded, could you give me a private session so I can send you the logins and everything please?
|
kisa
|
Also, I’m not sure if I’ve already mentioned this, but actually, I can no longer translate into English the listings that have different price variations because the mappings get messed up. If I don’t translate them, the assignment works correctly when switching languages, but of course, my product page is unfortunately not translated...
For example, in the original language my variations are in this order: A - B - C - D, but in English they get all mixed up, like D - A - C - B...
|
Lauren
WPML Supporter since 10/2015
Languages:
English (English )
Timezone:
America/New_York (GMT-04:00)
|
I have marked the next reply as private so that you can share credentials, thanks!
|
Lauren
WPML Supporter since 10/2015
Languages:
English (English )
Timezone:
America/New_York (GMT-04:00)
|
Thanks so much for providing the test site. I have set the staging site to minimal settings to try and rule out any conflicts. What I found is that the attributes are not added as Global attributes (I don't see Style attribute at Products -> Product Attributes. How are these attributes created - did you create them per product when you added the product? And how did you translate the terms? It looks like the WordPress editor is selected as the translation editor, which does not allow for automatic translation, and the terms do not show up at WPML -> Taxonomy Translation. If you can let me know how you originally translated them, that may help point me in the write direction.
To run another test, I deleted the English translation of hidden link and duplicated it. Once I did that, the prices and order seem to match up here: hidden link. Not that this is a solution per say, but it leans towards the idea that perpahs a third party plugin interfered somehow with the translation, which is why it will be helpful for me to understand how the translations were originally done.
After that, I ran the troubleshooting steps from the Woocommerce Multilingual section here hidden link
I couldn't easily find another product where the issue was happening, the one from our original chat did not appear and returned a page not found error. Is there another specific product that I can check to see if the troubleshooting steps resolved the issue on any other product?
|
kisa
|
Hello Lauren,
Thank you for your reply!
To answer your question, each attribute is entered individually on the product page because all our products are unique and have different attributes. That’s why we cannot define them globally across the site. At the same time, we always translate these attributes alongside the product description using the WPML translator.
I’ve indeed tested it: every time I delete the English WPML translation, the variations work properly. However, this means we lose the translated English page.
To give you another example, on our site, for product TH29892, the variations have the same price, so everything works fine. However, you can notice that, unlike the original version, in English the variations are all out of order. And if the variations didn’t have the same price, they wouldn’t function properly.
Another example is for product TH95614. We added a new color variation "lavender" to the site, which we translated, but it does not appear in the English version. (Added on our live site, it was after the creation of the test site, you can see it there)
I hope this clears things up, but feel free to let me know if you need more details or additional tests.
|
Lauren
WPML Supporter since 10/2015
Languages:
English (English )
Timezone:
America/New_York (GMT-04:00)
|
Yes, I can see that the variations not having the same price is the issue. I guess what I'm trying to determine is when the wrong price happened. Did you first translating using WPML and then edit using the WordPress editor? I ask this because when I got access to the site, the WPML translation editor was disabled.
On this test site, with minimal settings, can you try creating a new product the same way you do on the live site? Let's test these two things. The only reason I'm asking you to test instead of myself is because I want to make sure that the exact same steps/process is followed.
Without activacting any other plugins, please try this on the staging site:
1. Create a new variable product and add the attributes/variations. Translate it using the WPML translation editor. Does the same issue with wrong order/wrong prices happen?
2. Update a product on the staging site that already has variations. Add some new variations and then update the product and the translation. Do the new variations display on the front and have the correct pricing?
If we can't reproduce these steps in the staging site, then likely it is a conflict and we can next begin activating other plugins one at a time to see when the issue returns. If we CAN reproduce it in minimal settings, I'll escalate to our second tier to have someone take another look with me.
|
kisa
|
Hello Lauren,
regarding our product page creation/translation process: we first create the full product page by clicking on “Add Product,” and once it's published, we translate it into English using WPML. I just created a new product page for a pair of sneakers that have the same price, but on the live version of the site, the variations are all jumbled in English—whereas here, they aren’t, so it’s working correctly.
Two things are different, though:
- The WPML translation editor on the staging site has me translating entire paragraphs.
- Strangely, I didn’t have to translate the variations—they didn’t appear in the WPML translation editor.
For the point 2 : I added another color to the product TH95614, just like on the live site, then translated it into English — but this new color doesn’t appear in the English version.
|
Lauren
WPML Supporter since 10/2015
Languages:
English (English )
Timezone:
America/New_York (GMT-04:00)
|
I can see the new lavender not showing up for the product on the test site, thanks so much for testing this for me. I'm escalating to our second tier to try and determine what could be happening here, and I"ll update as soon as possible.
|
kisa
|
Thank you, Lauren. We're really stuck here because this issue is preventing us from having our listings with variations in English.
Regarding the first issue (variations showing in the wrong order and with incorrect prices), it seems to be working correctly on the staging site, not on the live site.
Do you think this might be related to the other problem?
Thanks in advance for your help!
|
Lauren
WPML Supporter since 10/2015
Languages:
English (English )
Timezone:
America/New_York (GMT-04:00)
|
I think the issue with the wrong order and with incorrect prices was coming from a conflict with another plugin. The reason I think that is because it's not happening on staging now that all other plugins are disabled. The best way to test and confirm this on the staging site is to activate the plugins a few at a time and see when the issue returns. I recommend activating 5 or so at a time, that way when the issue comes back we can narrow down the culprit. If you are able to do that, please let me know if you find a conflict that returns the issue. Meanwhile I'm working with our 2nd tier to dig deeper and figure this thing out.
|
