• Resolved dmarin

    (@dmarin)


    WooCommerce AUTO UPDATE to 8.9.3 created major problems on our site, just like several other users reported in the thread.
    Our website is https://tahocenter.si and the webshop page is: https://tahocenter.si/spletna-trgovina/

    Here are the details:

    1. The website loading time has slowed down considerably after the automatic update to 8.9.3 … both backend and frontend, indicating errors in the background as confirmed in log files (eg. PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in …/public_html/wp-includes/functions.php on line 4902 and many similar errors!).
    2. Web shop and some other posts pages are NOT accessible: first it was reporting Internal Error 503 when accessing web shop page:

    Service Unavailable
    The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
    Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.

    1. After some attempts to fix it based on forum discussions and suggestions, the page was completely blank (white screen of death!). The same happens if I try to view news posts on the page!
    2. The funny thing is: it only happens if I am NOT logged in as ADMIN! So, visitors are NOT able to access web shop and some other parts of website.

    So, why did Woo even force AUTO UPDATE?!?

    I kept reading forum posts and WooCommerce info about 8.9.3 update in came to info about Order Attribution feature introduced in ver 8.5 and the bugs introduced in 8.8 and 8.9 versions. I tried to disable Order Attribution feature (not even sure why it is there?), but it did not help in my case.

    I had to DOWNGRADE WooCommerce all the way down to 8.41 with WP Rollback plugin to get the website back to working state, but still have the problem with Webshop that is NOT opening!!!!

    I also checked the WooCommerce system report and settings and found problem with two older plugins:
    Hyyan WooCommerce Polylang Integration and Aelia WooCommerce EU VAT Assistant. But after disabling both plugins, the problem grew even worse: website became completely INACCESSIBLE, getting error 500, saying:

    This page isn’t working
    tahocenter.si is currently unable to handle this request.
    HTTP ERROR 500

    I have since replaced the Aelia EU VAT plugin and re-enabled Hyyan WooCommerce Polylang plugin to get at least home page to work.

    So, it seems something went wrong with the latest WooCommerce update.
    Is anybody else experiencing the same symptoms?

    Please, don’t give me general solutions because I spent last 8 hours trying just about everything possible. Either provide a FIX for this major problem that ver 8.9.3 created or reverse the changes that are causing complete websites crashing!!! Until ver 8.9.3 everything worked just FINE.

    Please HELP! I need somebody, HELP!!!
    Regards, Danijel

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hey there, @dmarin! Thanks for contacting us. I’m happy to help you.

    I’m sorry you are facing these issues after the last update. I understand this is a very frustrating situation and we will do everything we can to help you solve it as soon as possible.

    Since the website is not working at the moment, I suggest trying a clean install to see if the issue persists.

    Can you please try temporarily deactivating all plugins and switching to a default theme such as Storefront.
    Then please remove WooCommerce (don’t worry, you won’t lose any data by doing this).

    Now please download WooCommerce again and activate it while having no other plugins on and being on Storefront to see if the issue persists.
    I’d recommend first testing with 8.9.3. but if you prefer to use an older version you can download 8.9.2 here. But if you choose the second option, please make sure to disable order attribution.

    If everything is okay, then please first switch back to your theme, and then activate other plugins one-by-one, checking if the issue comes back.

    Please let us know how it goes.

    Have a wonderful day!

    Thread Starter dmarin

    (@dmarin)

    You know, funny thing is: OUR website worked just FINE until YOUR AUTO UPDATE CAUSED website(s) to CRASH. But now you want me (and others) to waste our time by disabling all our plugins, so you can prove that other Plugins and/or Themes are bad and not your newest version of WooCommerce.

    I am very disappointed with kind of “generic” support that does not care about our time. You know, I am sure that the new version works just fine on a blank WP website with default Theme. But it would be nice if your developers would test new releases with wider variety of Themes and Plugins. That way you would show respect for clients that use a wide variety of Themes and Plugins to make things work. For example we are using DIVI Theme/Builder for for this site and many various plugins to make it all work. If I disable DIVI, the site is basically dead.

    So, do you have any better suggestion? Or are you saying that the latest version of WooCommerce is not compatible with DIVI Theme and many popular plugins any more?

    Please respond ASAP.
    Thanks.

    Hi there @dmarin

    The changelog reveals the changes with each version of WooCommerce. A security reason was behind the 8.9.3 release. For further details, feel free to take a look at this announcement.

    Moreover, we make available various developer resources, like this handbook, along with developer documentation. Ensuring a WooCommerce extension is compatible and interoperable with the core platform is a task for the developer(s) of each extension. Likewise, the upkeep of a store is a responsibility of its owner/administrator, ultimately.

    That said, the errors reported here sound related to the server set up at the store, and the Divi theme currently in use. Feel free to reach out to the support channels of the site’s hosting provider, and Divi, as they would be in a better position to assist you.

    I trust this provides clarity. If you have more questions, let us know.

    We’re happy to help.

    Thread Starter dmarin

    (@dmarin)

    Are you saying that DIVI Theme/Builder is NOT compatible with WooCommerce any longer? Elegant Themes claim that it is. So, it seems that many changes in recent versions of WooCommerce are causing all these problems! And again, why force auto update if I do updates by myself??? The security issue is related to Order Attribution that we did not need anyway and it should not be added to WooCommerce if it was not thoroughly tested, because we, the users and developers, are not your test bunnies!!!

    So, I updated the WooCommerce to 9.0.0 and now have even more problems … in fact, the site is completely inaccessible because of new errors, one of the main ones being the problem with functions.php file:

    Notice: ob_end_flush(): failed to send buffer of zlib output compression (0) in /home/tahoce47/public_html/wp-includes/functions.php on line 5420

    Any idea why this kind of error? And what do you suggest we all that have problems with latest versions of WooCommerce do?!?

    blacksnow

    (@blacksnow)

    Our website was down during the latest 9.0 automatic update. We only need one response from woocommerce, how do we ensure the plugin can stop the automatic update and respect the plugin users, they have the right to choose whether they should update the plugin in a safe way.

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @blacksnow,

    I’m so sorry to hear that your website was down due to the latest automatic update.

    However, as this thread focuses on a different issue, I suggest that you start a new thread with your case, so that we don’t mix several troubleshooting sessions in one thread.

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @dmarin,

    We’ve not heard back from you in a while, so I’m marking this thread as resolved. Hopefully, you were able to find a solution to your problem!

    If you have further questions, please feel free to open a new topic.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.