Issues with todays update

I can confirm the issue on my end. Plugin fails to update and .maintenance file is not being removed, site went down.

Hello @zkingdesign

Given the details you’ve provided, it seems like there could be a compatibility issue with the latest version of WooCommerce and your current environment.

I suggest switching to a default WordPress theme, and then deactivating all plugins then try to re-update WooCommerce. If it works, that means a theme, or a plugin is contributing to the issue. Re-enable each to see which one causes it. You can find a more detailed explanation of how to do a conflict test here.

If you’ve identified the plugin or theme causing the issue, it’s best to reach out to the theme’s developer for support.

Let us know how it goes!

But i already posted that i use NO PLUGIN when updated. As for theme, if Kadence is to blaim (i don’t believe that), i can’t disable or change it.

I moved back to 8.2 and i will stay there for now. A very bad update 8.3. very bad.

Hello @dimalifragis,

I can imagine your frustration. Please note that version 8.3.1 was released yesterday specifically to address some bugs. Would you mind giving it a try while switching to the default Storefront theme?

If you’re not comfortable switching the theme on the live version of your site, you can create a staging environment using WP-STAGING.

[22-Nov-2023 01:08:33 UTC] PHP Warning: foreach() argument must be of type array|object, null given in /home/public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/BlockPatterns.php on line 254

Regarding the warning, it’s unlikely to be what’s causing the site to break. Warnings serve as alerts that something isn’t quite right, but in most cases, everything still functions as expected.

That said the team has already addressed this issue. It was related to the WooCommerce Blocks package. Since WooCommerce Blocks aren’t regularly merged into the WooCommerce core to maintain stability, you can remove the warnings by installing the dedicated plugin until version 11.5.2 is integrated into the core (where the issue was fixed).

It would be great if you could install the WooCommerce Blocks plugin before updating the WooCommerce core to confirm if this indeed caused the issue.

PHP Notice: Function FeaturesController::get_compatible_plugins_for_feature was called incorrectly. FeaturesController::get_compatible_plugins_for_feature should not be called before the woocommerce_init action. Backtrace: activate_plugin

This is also reported here, but it’s just a notice so you can ignore it.

Look forward to hearing back from you.

@babylon1999 Thank you for your time. Appreciated.

Somehow it feels unsafe all that and i’m back to 8.2.x. All ok, probably 8.3 needs some time.

I have the same issue with latest WC (8.3.1).

Hi @titsmaker

Sorry to hear that you are experiencing the same issue.

As my colleague mentioned, these are known issues our developer already knows about. However, it’s important to note that we’ve resolved one of these issues in the latest version while another one still remains open.

Could you help us by clarifying the warning you’re receiving?

However, to align with forum best practices, please create a new topic so that we can address your issue(s) separately.

You can create a new thread here.

Make sure to include a copy of your site’s System Status Report in your thread. You’ll find it at the top of the page under WooCommerce > Status > Select Get System Report and then Download for Support. This will download a TXT file containing the SSR’s contents to share with us. Once you have the System Status Report file, you can copy and share it via Mozilla Community Pastebin and share the link.

Thanks for understanding!