Either I missed explicitly stating that I published the duplicate product after I tweaked it, or you missed that part. Either way, I obviously know the duplicate is initially created as a draft. So I make my tweaks, then I publish it before I translate it. I feel like I've already covered this at least once and that you are completely missing my point. It seems like you are bound and determined to find a way to blame this on user error, rather than consider that the product may have a bug.
If you are arguing that because the product was initially created as a draft, the translation will always be created as a draft regardless of the product's published state at the time the translation is created, that is absolutely not expected behaviour.
For one, the setting that I was asked to check begs to differ. Second, all posts, pages, and products are initially created as drafts, but their translations are not created as drafts as long as the post has been published before the translation is created. There is no contention that everything (including duplicates) is initially created as a draft; that is the point of the draft state. The contention seems to be about what is expected behaviour once the post has been published. My experience (and that setting seems to confirm this) is that as long as the post is published when I create a translation, the translation is created in a published state as well, except for duplicated products.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
When duplicating a product in WooCommerce, it will be created as "draft". This is also the case when testing without WPML.
WPML will sync the post status only when the translation is created for the first time, or in this case, once the duplicate is created.
I provided a snippet in an earlier comment that lets you prevent a translation from being created once you duplicate a product in WooCommerce.
When creating a duplicate in WooCommerce, the translation is created together with the duplicate, and this is why the post status will not sync any longer, as it was already synced on duplication.
This is expected behavior, which was confirmed by our Compatilbity Team Lead.
Most WPML users currently expect this behavior, as they want to be able to use independent post statuses after the content has been translated or duplicated.
I also provided a snippet in a previous comment that will allow you to alter this behavior and keep post statuses in sync between original content and translations.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
You can enable the option WPML > Settings > Translated documents options > When you publish the original post:
- Publish the post translations
If enabled, and you have original content saved as a draft, then publishing this original content will also publish the translation. This also works for products.
See that is the core of the problem. I've got that set, I'm publishing the duplicate, then I translate, and the translation is stuck on draft.
To recap:
1. WPML > Settings > Translated documents options > When you publish the original post:
- Publish the post translations: set to enabled
2. Product post is duplicated, edited and THEN PUBLISHED
3. Click on the edit translation, which takes me into the ATE, click save and continue
4. After completing the ATE I'm back in the duplicated product where I click on update then exit the block editor.
5. observe the translated post is in draft mode. This is horrible UX, whether by design or if it is a bug.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Thank you for the detailed steps!
On my sandbox:
1) Duplicate an original product that is translated in WooCommerce
2) WooCommerce will create a draft, and WPML will also duplicate the translation as a draft
3) The original product is published, and at the same time, the translated product is also published.
This works as expected on my test
Exception where the translated product is not published:
1) Duplicate a translated product in WooCommerce
2) WooCommerce will create a draft, and WPML will also duplicate the original as a draft. Only now, you have actually duplicated the translation with WooCommerce, and WPML duplicated the original product.
3) Then you publish the translation, but the original remains as a draft.
This is exepcted. WPML only syncs from the original content to translation.
This means:
I can only replicate this issue on my sandbox if I duplicate a translated product in WooCommerce.
One-Click-Login: hidden link
So, in this case, it would not be expected to duplicate an actual translation. The original product should be duplicated instead.
You can recognize an original by the fact that it has translation method options inside the right sidebar of the WordPress Editor.
Please take a look into this video, which I recorded for you: hidden link
Ok I can't argue if this expected behaviour since I know nothing about the design. However I'm sticking with my opinion that this is an undesirable behaviour and horrible UX, regardless of it is expected or not.
I was talking with Alejandro via email who wasn't as sure as you that this is expected behaviour. He said he was to talk to you about this ticket so the two of you could decide next steps together. He seems to agree with me that bad UX is a bad thing.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Could you please confirm if the issue occurs because you are duplicating a translation, and not the original product?
Also, please take note that I already created a feature request for adding a new option to WPML that will allow you to keep the post status always in sync. It is now in the hands of our product manager and the developers to decide if such a feature will be made available or not.
I provided a snippet earlier on this ticker, which can be applied to your site to solve this.
I always duplicate the product in the origional language, not the translation. Sounds like there is nothing more to be done under this ticket. If you don't plan on doing any more troubleshooting on this, you may close this issue, and I'll delete your access.
