Timmy Crawford

@connor234 I’m able to reproduce the error on one of my test sites. I’ll get an issue logged and work on a fix. Thanks for the bug report.

@dhunink I really appreciate you taking the time to leave a positive review! That is awesome to hear you are running it on multiple stores too!

If you do encounter any problems, or have some feature suggestions, please do let us know.

@jonathanemms sorry you felt the plugin was buggy. Could you provide some more details about features that you felt were broken? FWIW we have been running this in production on woocommerce.com and I personally run it some other sites in production.

That being said though, each WooCommerce install is quite unique – extensions, hosting environments, and other WordPress plugins can all result in different experiences. So if you can share some more about the bugs that you encountered I’d be happy to help troubleshoot and seek out solutions.

@gamefreakbaree sorry you had problems removing the plugin. By chance do you recall which version you had installed?

@lppicture apologies that you encountered issues with the historical data import process. I’d be happy to help you with the process if you would like – just let me know.

@aboutwebsites thanks so much for that info. Would it be possible for you to create a support/test account for me to check things out further?

@comcart thanks for giving an update here. The default job processing for ActionScheduler uses WP-Cron to process the queues ( https://actionscheduler.org/faq/ ). So depending on your configuration and the number of legacy orders/customers to import, this could take quite some time to process.

You can also process the queues via WP CLI, which is massively faster, and would allow you to dedicate a specific server to run jobs if that would make the most sense for your environment.

How many sites are you in your network? If you’d rather to chat via email let me know!

@younes89 that is a huge help, thank you. I’ve seen another report of this same error message. Is this happening only on the new Dashboard page, or is it also occurring on all the new Analytics/Report pages?

Also curious, if you can look at the network tab in your browser console, filtered by XHR – if any of those API requests are returning a non 200 response.

@napathello I’m having problems re-creating the bug – which locale are you using?

@fencer04 we have had a few reports of numbers not matching to legacy reports. Some of these have been due to stores using custom order statuses that need to be updated in Analytics > Settings to ensure the new reports will count those orders in the reports.

It could also be other extensions installed on the site that are manipulating the legacy reports in some way.

Do any extensions come to mind that might be causing this on your site?

If you are open to the idea, I’d also be happy to look into what the cause might be if you have a staging site or are comfortable with creating a support account for me to look with.

@bncpeter –

> Do you have any advice on how they can be removed? Would the plugin have left anything else behind?

All pending jobs and data used to generate reports in this plugin are removed upon deactivation.

FYI other parts of WooCommerce core ( and extensions ) use ActionScheduler to enqueue background jobs – webhook processing is one of these things. So depending on store’s usage of Webhooks you could encounter a similar behavior there.

ActionScheduler 3.0 is going to move away from using a custom post type to a dedicated database table to track jobs. When that is ready, there will no longer be any entries in wp_posts for job processing. We will be certain to highlight that change when it is ready in the release notes on the dev blog.

@sc456a thanks for the candid feedback. We have tested the plugin, and specifically the historical import process, across a variety of webhosts ( shared to dedicated ) and are also running the plugin on WooCommerce.com – but we most definitely can not test every distinct store configuration that exists online. My apologies that your experience was not a positive one, and if/when you would like to try it again and encounter any issues please give me a ping so I can help out.

Currently there is not a way to disable/remove the new header. I’ve logged this as a feature request on the project if you would like to follow along:

https://github.com/woocommerce/woocommerce-admin/issues/2453

I’m going to mark this as resolved since we are now tracking the feature request on GitHub.

@celulanerd sorry you are having issues with the plugin. I’ve just attempted to recreate the bug myself and have not been able to do so. Is the error happening on all WooCommerce Admin pages, or just the Dashboard?

Hello there @alfonsofeb – the Stock “Activity Panel” is designed to show products that are low / out of stock. Are you saying it isn’t showing a full list of out-of-stock products?

There is also the new stock report which can be used to filter products by stock status: wp-admin/admin.php?page=wc-admin#/analytics/stock?type=outofstock