I have this fatal error on updating woocommerce from 9.5.1 to 9.5.2. I rolled back but still getting code 500: 2025-01-09T08:00:23+00:00 Critical Uncaught Error: Class “WC_Notes_Refund_Returns” not found in /data/sites/web/mysite/www/wp-content/plugins/woocommerce/src/Internal/Admin/Events.php:132 Additional context { “error”: { “type”: 1, “file”: “/data/sites/web/mysite/www/wp-content/plugins/woocommerce/src/Internal/Admin/Events.php”, “line”: 132 },
At this time I am trying to put back a backup to fix it
This topic was modified 4 months, 1 week ago by dyin.
This topic was modified 4 months, 1 week ago by dyin.
further update: I called my host as uploading the backup didn’t fix it immediately. apparently, there was an error in my htaccess also that caused a redirect. It kept pointing to the french site while trying to load the dutch version. So something really went wrong with the update combined with my multilingual setup
[Thu Jan 09 10:01:28.468945 2025] [error] [pid 1372259] core.c(4073): [client 2a02:a03f:adba:bc00:4958:4fbc:2b57:e73:0] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace.
I can imagine how frustrating it must have been to encounter this error after the update. To resolve the issue, let’s go through a few troubleshooting steps.
First, clear your server cache, browser cache, any cache from installed caching plugins, and, if you’re using a CDN, clear its cache as well.
Next, update WooCommerce to the latest version and regenerate the .htaccess file. You can do this by going to Settings > Permalinks in your WordPress admin and clicking “Save Changes” without making any modifications. This will rewrite the .htaccess file with the default rules.
Once you’ve done these, please let me know if the issue is resolved.
@mosesmedh Those where the steps I did before I even started reverting to the old version. The only thing I may not have done at the time before contacting my host was regenerate the .htaccess Although I know that trick rather well so I cannot imagine why I would not have done so.
I encountered the same issue today. Fatal error. The only way was to push a complete restore from backup, wp files and db which replaces everything.
After that, I updated wc again, but this time it didn’t show the fatal error strangely. Instead, the pages checkout, login and register on front-end were showing a 404 error, checked pages are there in backend, then, went ahead to permalinks and saved that twice, still 404 error, then the add to cart button on simple and variable products disappeared, and in products in backend, the product variations with their stocks and prices fields was empty which I think was causing the add to cart button to disappear from front end.
The only thing left was to rollback wc to version 9.5.1 and luckily that resolved all the issues above.
Surely there is definitely a problem with wc 9.5.2.
Hoping to help others by sharing the kind of errors that popped up in my store and for the devs to test and try to find the root cause.
Seeing woocommerce/woopayments payment failure issues since this update to 9.5.2 couple of days back.Have tried sending the logs to support team but nothing has come out of it yet. Have tested by disabling all plugins except woocommerce and the issue persists. The only thing I havent done yet is use the default theme and testing but the weird part is that the issue isnt for all the orders but only impacts some – and there isnt really a defined pattern.
I understand your concern. I’ve tried to replicate the issue on my site, but I wasn’t able to do so. It seems there might be a plugin or setting on your site triggering the issue.
Upon further investigation, I found that another user reported a similar issue when using WooCommerce and WPML: GitHub issue #54364. To verify, are you using the WPML plugin on your site? If so, could you please deactivate the plugin for testing and see if the error message persists?
Additionally, for further testing, could you please deactivate all plugins except for WooCommerce and check if the error message reappears? This will help us determine if the issue is related to a plugin conflict or if it’s specific to WooCommerce.
If you’re using WPML, I would recommend submitting your comment on the GitHub issue here, so our developers can assist you further.
Could you please share the ticket link that you have created and haven’t received a response to yet, so that we can assist you in resolving the issue on your thread?
