Hi @joyryde,
Thank you for reaching out and bringing this to our attention. I understand how concerning this can be for you and your business operations.
The fatal error you’re seeing is indeed related to WooCommerce, but several factors could have caused it — from custom code or snippets on your site, to plugin or theme conflicts, or even a corrupted WooCommerce update.
To better assist you, could you please share your site’s system status report (via WooCommerce > Status > Get system report > Copy for support)? Also, let me know if this error has visibly broken anything on your site or affected how you interact with it.
Hello!
There are zero issues on the status report, we have been using Woocommerce since the day it was released to the public, and know it very well. The hosting company said to report this flaw to WordPress, so we did.
Hi @joyryde,
Thanks for following up, and I completely understand where you’re coming from. It’s clear you’ve been working with WooCommerce for a long time, and I appreciate you taking the time to report this.
Even if your system status report shows no visible issues, having a copy of it will still help us understand your site’s setup, like active plugins, overrides, and server environment, which can all influence how this kind of fatal error shows up.
Could you also let us know if this error only started recently, possibly after updating WooCommerce to version 9.9.3 or making other recent changes?
Once you’re able to share the System Status Report (via WooCommerce → Status → Get system report → paste it at https://pastebin.com or a similar tool), we’ll be able to guide you through the next steps for identifying the root cause and resolving the conflict.
Looking forward to your update!
@joyryde did you refund that particular order? we are getting similar errors on one of our websites and it is only affecting an order that had a partial refund, every other order is fine.
@blkout
We can’t check that because Woocommerce causes this to happen if we attempt to access the order URL:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at [no address given] to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Hi @joyryde ,
I’m really sorry to hear you’re having trouble accessing the order from the URL—that definitely shouldn’t be happening.
To dig into this further, we’d need a copy of your site’s System Status Report. That’ll help us get a better idea of how things are set up. Also, just to check—are you using any order-related plugins that might be interacting with WooCommerce?
Have you had a chance to try a conflict test yet? If not, here’s what we’d recommend:
Please deactivate all plugins except for WooCommerce, switch to a default theme like Storefront, and temporarily remove any custom code if you’ve added some.
You can follow this guide to run a full conflict test: https://woocommerce.com/document/how-to-test-for-conflicts/. This will help us pinpoint whether something behind the scenes—like another plugin or theme—is causing the issue.
Also, I came across a similar case in another support thread, where the issue seemed related to Object Cache. Can you confirm if your site is currently running with object caching enabled?
Let us know what you find after checking those points, and we’ll go from there!
Hi there,
As there’s been no follow-up, I’ll consider this resolved for the time being. We’re happy to jump back in if anything comes up!
If WooCommerce has been useful for your store and you appreciate the support you have received, we’d truly appreciate it if you could leave us a quick 5-star review here: https://wordpress.org/support/plugin/woocommerce/reviews/#new-post
Hello –
Cloudways Hosting uses Object Cache on all websites, it’s mandatory.
Disabling Object Cache on the server does not fix this flaw, you still cannot access any URL of any Woocommerce order that has been trashed, it just shows:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at [no address given] to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Hi @joyryde ,
Thanks for sharing both reports. I’d be happy to help you troubleshoot them.
Regarding the first issue with the fatal error in class-wc-order.php:
This can sometimes be triggered by a partial refund, especially if the refund data was stored in an unexpected format. Could you check if this happened on an order that was partially refunded? If so, please open that specific order in the admin dashboard and let us know if you notice anything unusual—like missing or duplicated line items.
As for the second issue, where visiting a trashed order URL results in a 500 Internal Server Error:
Since you’re hosted on Cloudways and object caching is mandatory, I recommend contacting their support team and asking them to check the server error logs for any PHP-related issues when accessing trashed order URLs. That should give us more insight into what’s happening behind the scenes.
Once you have that info, feel free to share it here and we’ll take it from there!
The hosting company says that clicking this link to a trashed order results in this:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at [no address given] to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.Apache/2.4.63 (Debian) Server at nomadicsupply.com Port 80
And nothing appears in their Apache error log.
Hi @joyryde
Thanks for following up and sharing that detailed feedback. I understand how frustrating it must be to deal with a persistent 500 error, especially when your hosting team isn’t seeing anything in the server logs.
I ran a test on my end and everything works as expected. When attempting to access a trashed WooCommerce order’s edit URL, WordPress displays: “You cannot edit this item because it is in the Trash. Please restore it and try again.” It does not result in a 500 Internal Server Error.
To help us understand if this is limited to WooCommerce orders or part of a broader issue on your site, could you try the following:
- Trash a regular page or post, then try visiting:
- Its frontend URL
- Its edit URL in the admin (/wp-admin/post.php?post=ID&action=edit)
- Let us know if either of those URLs also triggers the same internal server error.
Alongside your test results, please share your System Status Report by copying it from WooCommerce → Status → Get system report, then paste it at https://pastebin.com/ and send us the link.
That’ll help us dig deeper and determine whether this is environment-specific or something else in play. Looking forward to hearing what you find!
