The following threads were all posted in the last 24 hours, and they all involve critical errors with the latest version of woocommerce. Many are having to rollback to 8.4, just to even have a functioning website.
1.) Why was such a buggy version released to begin with? The amount of people reporting errors with this latest release isn’t typical of previous releases. Why hasn’t there been at least an official notice or advisement addressing this in the interim?
2.) When will it be fixed?
3.) Why, despite the obvious, major issues and growing number of threads, has there been little to no response here on the support forum?
I suspect what’s on the forum is only the tip of the iceberg, Personally, my phone has been blowing up all day with people desperate for help with their dead WooCommerce site.
Also, I want to add that there is a problem with woocommerce analytics. There are just blank pages. And in the error console ReactDOM.render is no longer supported in React 18. Use createRoot instead. Until you switch to the new API, your app will behave as if it’s running React 17.
If your site has gone down, here’s some helpful information I was able to find.
Here’s a step-by-step guide:
Deactivate WooCommerce: If you can access your WordPress Admin, navigate to ‘Plugins’, find WooCommerce, and click ‘Deactivate’.
Delete the Current Version: After deactivation, click ‘Delete’ to remove the current version of WooCommerce. Don’t worry, your data is safe.
If you can’t access WordPress Admin: Access your WordPress files with FTP/SFTP/SSH/File Manager and remove the directory: /wp-content/plugins/woocommerce
Install the Downgraded Version: In your WordPress Admin, go to Plugins > Add New > Upload Plugin. Upload the file you just downloaded and activate the plugin.
Check Your Site: Ensure that everything is running smoothly and that no data was lost during the downgrade.
(In my situation I had to manually remove the woocommerce folder, I was able to restore a backup of the folder) My path was htdocs/site/wp-content/plugins/woocommerce
I think the new tracking cookies (sbjs) implemented in V8.5.x are the cause for triggering modsec. This results in fail2ban jailing. These tracking method should not be implemented.
For those still having issues, try option 3 below, it’s a quick and easy setting to test:
What action should I take?
Pleskalready has a help article targeting this issue, identifying Comodo rule with ID 218500 being false-positively triggered when Woocommerce 8.5 is in use. They recommend disabling the rule following the steps on their page.
Check with your host to see if ModSecurity is enabled. If that is the case, you may ask your host to adjust the firewall rules to allow the cookies set by Woo’s Order Attribution feature. You can find more information about the cookies used by this feature in our documentation.
If the above doesn’t work for you, disable the Order Attribution feature to prevent future users from seeing the 403 errors by going to WooCommerce > Settings > Advanced > Features and toggling the Order Attribution feature off.
Half of the fatal errors people are seeing have nothing to do with these security settings. They have to do with Woo’s own Stripe plugin. Updating that will fix half of these issues. Although I’m not doubting the other half of the issues people are experiencing. 8.5+ is a mess.
For further solutions, please refer to these steps below:
Pleskalready has a help article targeting this issue, identifying Comodo rule with ID 218500 being false-positively triggered when WooCommerce 8.5 is in use. They recommend disabling the rule following the steps on their page.
Check with your host to see if ModSecurity is enabled. If that is the case, you may ask your host to adjust the firewall rules to allow the cookies set by Woo’s Order Attribution feature. You can find more information about the cookies used by this feature in our documentation.
If the above doesn’t work for you, disable the Order Attribution feature to prevent future users from seeing the 403 errors by going to WooCommerce > Settings > Advanced > Features and toggling the Order Attribution feature off.
