Orders page bug after WordPress 5.0.2 Update

Same problem!

Same problem here! Also, I did not get a notification email of a new order being produced.

Same here!

Same problem here! Any workarounds for the orders list table?

Only “All” orders view is broken. If filtered by status (by links on top), then orders show up.

Same

Hi all!

(@martian36, @santiagom86, @newuser33, @lpburny, @indrektamming, @bigtrousers)

We’re aware of the issue and have found what’s causing this. We’re working on the fix right away as well. Thankfully you can still access orders based on their specific order status, so in the mean time I would recommend to use those statuses to help manage your orders. You won’t need to wait long as a fix will be released ASAP

Same with me

Same with me

This topic is closing since @ryanr14 and people in WooCommerce are aware of this issue.

Our business is still getting email notifications of new orders. Downgrading to 5.0.1 on a development site fixed the issue of no orders appearing in “All Orders” view. I would advise waiting for a fix from WooCommerce or WordPress.

• This reply was modified 5 years, 10 months ago by Ken Mick. Reason: added "is" to first line

Hah, thanks @martian36,

Not just me, all of us here at WooCommerce are. ??

Hi @kengmick,

It sounds like you are having a separate email issue, unrelated to the All orders screen showing no order as of WordPress 5.0.2.

If we can help out with this please do create a new post here in the forums. ??

Hi @ryanr14,

Thanks for message.
I’m experiencing the same problem as others in this thread, that the “All” Orders view is empty as of updating to WordPress 5.0.2.

@newuser33 mentioned not getting email notifications. We are receiving new order email notifications just fine.

Hi @kengmick,

Ahh, doh! I see what you were saying now, you’re still getting email notifications for new orders even though the All orders view is empty at the moment. Thank you for clarifying.

And @newuser33 we can definitely help troubleshoot your email issue in a new thread. We can see if it’s related to 5.0.2 or perhaps something else.

Thanks all!

Glad to found this topic, good luck finding the fix guys!