Woocommerce Fatal Errors on Updates

  • Three days ago, I moved to Woocommerce because EDD did not have the features I needed for payments. I was so incredibly happy with the way things were going. I even purchased an extension for some functionality that I needed. I was so excited!
    I noticed one of the plugins needed an update. It happened to be Woocommerce. So, I pressed the update button.

    I went back to my product page I was editing. I pressed view. 403 forbidden error. I tried other pages, same thing. What the heck happened?
    My entire site went down, from dashboard, to front facing pages, to products…everything.
    I went through the steps to fix: .htaccess, file permissions, plugin conflicts…everything and the kitchen sink. I then disabled Woocommerce and tested this. It turned out to be the latest update. I had to revert back to 8.4 for my site to work correctly again.
    I have since returned the extension and am looking for an alternative. This update was a joke and it says a lot about the product and the product team when they release a version that causes such catastrophic failures.

    • This topic was modified 10 months, 2 weeks ago by modernartbykj.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Sandip Mondal – a11n

    (@sandipmondal)

    Hi there,

    Sorry to hear that the update caused a fatal error. This was related to a bug found in WooCommerce 8.5:

    Since then 8.5.0 release was reverted back and now 8.5.1 is released.

    I’d recommend you consider disabling automatic updates on the live site and testing new changes/updates on a staging environment first before applying them to your live site. This approach can help you maintain a stable online store while exploring and adapting to new features, changes, and updates.

    We value your feedback, and we are here to assist you in addressing any issues you encounter. In case you see such errors, please do reach out, and we will be happy to assist you in resolving the matter.

    If you decide to give WooCommerce another try or if you have any further questions or concerns, please do not hesitate to reach out.

    same here.. reverted to 8.4… woocommerce caused to mod_security module on the server to refuse any connection requests to the site.. solved it after 6 hours..

    Thread Starter modernartbykj

    (@modernartbykj)

    @sandip
    I would never have auto updates! This was manual. Next time I will be using the staging area, but I am not confident in the product.
    And, it is both 8.5.1 and 8.5 that cause the issues. The latest version that works is 8.4

    Thread Starter modernartbykj

    (@modernartbykj)

    @spcspectre
    Fortunately it didn’t take 6 hours for me. Didn’t dive too much into the server issue since the only cause could have been the plugin update as I did that manually. I did investigate other possibilities as there were other anomalies on the server, but it all boiled down to the plugin updates having bugs.

    Actually Mr Sandip, nothing has changed… last week i had the same breakdown on one of my websites, but then i updated 5 plugins and wasn’t sure which caused problem… did rollback /restored site from backup.
    Today i had new notification about woo update so i did it with hope, that everything will be ok, it was not. Again 403 forbidden on all site and bunch of errors…

    So again i restored site and i turned all updates for some time untill i will make sure everything works, as Tutor LMS depends on Woocommerce i must have it… But i’m very upset.

    Plugin Support Sandip Mondal – a11n

    (@sandipmondal)

    Hi everyone,

    Sorry to hear that the plugin updated caused an issue.

    This issue has been reported here and our developers are aware about it:

    This problem is related to a new feature available since WooCommerce 8.5 called Order Attribution Tracking

    There are two ways that one can go about the 403 errors:

    1. In case you do not want to use this feature you can disable it. Info from FAQ Cookies are blocked by a Web Application Firewall (WAF)
    2. In case you want to use it then a specific WAF rule triggering the issue needs to be updated or disabled to allow proper functioning of the sites and the feature. For example, the following Plesk article explains how to do it: Plesk WP website is not accessible with the 403 Forbidden error after a WooCommerce plugin update. You can also reach out to your assist you with this.

    I hope this information helps.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Woocommerce Fatal Errors on Updates’ is closed to new replies.