Terrible plugin – doesn’t play with WooCommerce Partial Orders or PublishPress

I fully agree! I’ve had to clean up multiple scheduled actions

WooCommerce > Status > Scheduled Actions >

Be sure to follow the updated info on https://github.com/woocommerce/woocommerce-admin/issues/2364

Hello @carylwills,

If you use the PublishPress plugin your admin email account will be flooded with ‘wc_admin_unsnooze_admin_notes’ and ‘wc-admin_import_order’ email messages – thousands of them. It took me an hour to clean up my inbox.

Unfortunately, the PublishPress “notify when content is published” workflow indiscriminately sends emails for all post types. It seems that you’ll receive emails for any post type that transitions status, including DB updates performed by WooCommerce as well as WooCommerce Admin historical imports.

I believe this filter will stop notification on older version of PublishPress: add_filter( 'pp_notification_scheduled-action_status_change', '__return_false' );, but the latest version uses a different mechanism with no straightforward way to hook into.

While WooCommerce Admin’s usage of Action Scheduler (which is what caused this) is quite extensive, this “bug” looks like it can occur with any plugin that uses custom post types. This will ultimately need to be resolved in the PublishPress plugin.

Here’s another user who encountered the same issue, and decided to disable the notifications: https://www.ads-software.com/support/topic/wc-admin_proccess_order/.

If you use WooCommerce Partial Orders Pro, the banner displayed by WooCommerce Admin overwrites the top of the Partial Orders update screen. This is a pain and makes Partial Orders difficult to use. The only solution is to uninstall WooCommerce Admin.

Would you mind providing a screenshot of this issue so we can attempt to resolve it? Thank you.

Hi Jeff,
Here is a screenshot of the problem: https://snag.gy/QdXEjp.jpg
Here is a screenshot of the same window with WooCommerce Admin disabled: https://snag.gy/yRlC01.jpg

You can see that the Partial Orders ‘Close window’ cross in the second image is covered by the WooCommerce menu banner in the first image. This makes it difficult to use the Partial Orders features.

Hi @carylwills,

I just wanted to let you know we’re working on resolving this. It should be included in the next version of the plugin.

You can track the progress here: https://github.com/woocommerce/woocommerce-admin/pull/2431

Thanks for the screenshots.

PublishPress has logged an issue to track this: https://github.com/publishpress/PublishPress/issues/440

Irrespective of PublishPress, why does the action scheduler mindlessly burn through post IDs?

My order numbers used to be mostly sequential, now two orders placed an hour apart will likely have many gaps in between.

Irrespective of PublishPress, why does the action scheduler mindlessly burn through post IDs?

Action Scheduler uses a custom post type to represent actions, which caused the post ID to increment.

My order numbers used to be mostly sequential, now two orders placed an hour apart will likely have many gaps in between.

There are extensions that can restore this functionality: https://www.ads-software.com/plugins/woocommerce-sequential-order-numbers/

Don’t you think it would be better to avoid the use of a custom post type rather than add another plugin to work around the issue?

WP-Cron does not cause the same issues.

Don’t you think it would be better to avoid the use of a custom post type rather than add another plugin to work around the issue?

If you need your Order numbers to be sequential, the only way to do that is with a plugin – even if you’re only using WordPress + WooCommerce.

Custom post types are a common storage mechanism and can be found in thousands of plugins. WordPress Posts, Pages, Media/Attachments, WooCommerce Products, Orders are all posts and increment the ID value.

None of those post types are generated automatically every n minutes. They only occur on user activity, which is ideally less frequent than sales on a platform that is designed primarily for sales!

Skipping a handful of post IDs occasionally isn’t that annoying, but skipping tens between every single order is. In a few weeks of running this plugin I’ve skipped 14,000 post IDs.

@galapogos01 The next version of Action Scheduler will use its own tables instead of the posts table. Beta should be soon – https://github.com/Prospress/action-scheduler/pulls?q=is%3Aopen+is%3Apr+milestone%3A3.0.0 .

Thanks Ron.

Same problem here..

Indeed at woocommerce > status > schedule actions, there are multiple hooks wc_admin_unsnooze_admin_notes with with recurrence “every 1 hour”.
1300 of them, which they are triggering sucuri notifications each time.

Several threads reffering to uninstalling the woocommerce admin plugin..

And btw I dont use publishPress plug in as mentioned by the replies.

• This reply was modified 5 years, 3 months ago by abiox.

For those who use PublishPress we have a new beta package addressing this issue. We have planned a release for next week, but here is the beta package just in case you want to test it:

https://github.com/publishpress/PublishPress/releases/tag/1.20.9-beta.3

The problem is that when we released the notification workflow feature we allowed to suppress the post type, with the intention run the workflow for all the post types. After a few releases we added a form validation rule not allowing that any more, but some users still have the workflows without any specific post type selected in the filter. If that is the case we advise you to review your notification workflows making sure you select only the post types that are relevant for that workflow.

This beta makes sure PublishPress only run the workflow for “supported” post types, ignoring “scheduled-action” and other post types. But the advise above still applies to avoid undesired notifications.

If you have issue with PublishPress or with this beta, please, feel free to contact our support. Thanks

I have a dozen of these under ‘scheduled actions’

update_expiring_product_props Complete Every 1 day

is is safe to delete them?

• This reply was modified 5 years, 2 months ago by SSVapes.