[Résolu] Toolset WooCommerce Blocks published automated draft posts

[Auteur]

Publications

[pabloQ-2]

For quite a few days we have seen a strange phenomenon happening in our website.

Working with a post creates a published automated draft. It also happens when creating a new post, even if nothing is written anywhere (title, body, nothing).

And those published automated drafts are shown both in the backoffice (image 1) and in the frontoffice (image 2).

To try to isolate the conflicting plugin I deactivated all of them and then activated them one by one. And I was finally able to point to a presumed guilty: Toolset WooCommerce Blocks.

When this plugin alone is deactivated, those automated published drafts disappear from the backoffice (image 3) and the frontoffice (image 4).

I have no idea why Toolset WooCommerce Blocks seems to be the plugin causing this. Maybe it's a bug that needs to be fixed.

[Luo Yang]

Hello,

I have tried it in a fresh WP installation + the latest version of Toolset plugins.

See below test site:
lien caché

When I create a new post, it will only create one Auto draft post
lien caché

And it is WordPress built-in feature, you can follow WP document to disable it:
https://developer.wordpress.org/apis/wp-config-php/#disable-post-revisions

[pabloQ-2]

Hi Luo!

Thank you for your answer and for the test site.

I have deactivated Toolset WooCommerce Blocks on the test site.

How come now there are no auto draft post seen in the frontoffice ( lien caché ) and in the All tab of the Posts section in the backoffice ( lien caché ) ?

There must be something happening with that plugin. Could you please check it?

[Luo Yang]

The draft posts won't display in frontend by default, as you see in the sandbox website, there isn't draft posts in frontend.

I assume you can not reproduce the same problem in above sandbox website too, so there might other compatibility issue in your website, please check these in your website:
1) Deactivate all other plugins, switch to WP default theme 2023, and test again
2) If the problem still persists, please provide database dump file(ZIP file) of your website, you can put the package files in your own google drive disk, share the link only, I need to test and debug it in my localhost

[pabloQ-2]

Hi Luo Yang,

I am totally able to reproduce the problem within the test site.

On the test site, I have again activated Toolset WooCommerce Blocks.

Now you can visit the Homepage of the test site and you will see the published auto draft posts.

This ONLY happens when Toolset WooCommerce Blocks is activated. If not, posts are not shown (which is the correct way).

Please check really it.

[Luo Yang]

Thanks for the details, I can see the problem in sandbox website, I am checking it, will update here if find anything

[Luo Yang]

I have tried it with the latest version of Woocommerce plugin + Toolset plugins, it works fine:
See below test site:
Login URL: lien caché

4 posts in draft status:
lien caché

All of them won't be displayed in frontend:
lien caché

And WordPress posts can have only one post status, it won't be in both draft status and published status.

[pabloQ-2]

Hi Luo!

Thank you for your answer and sorry for the delay.

The issue still persists. I have seen in on my own websites and I have been able to reproduce it within your test site.

See how an auto draft is shown in frontend:

lien caché

To reproduce it I have just clicked on "Add new" under Posts section in the backoffice (here: lien caché ).

Something is not working. Please take a look into it.

[Luo Yang]

It seems the latest version of Woocommerce plugin fixed this issue:
https://wordpress.org/plugins/woocommerce/#developers

And I have tried it again in above sandbox website by upgrading Woocommerce plugin the latest version, it works fine now.
Here are the detail steps:
1) Login into above sandbox website:
lien caché

2) Goto URL:
lien caché

3) Test it in frontend:
lien caché
I don't see any auto-draft posts in frontend, see my screenshot

[pabloQ-2]

Hi Luo!

Thank you for your message. It seems that, as you say, the last WooCommerce update solves it.

Still seems strange altogether but hey, no questions asked.