Rodel Calasagsag a11n

Hi @magicpowers. Quoting from the WooCommerce 9.3.1: Dot Release announcement:

WooCommerce 9.3 was never set as the stable version

And I hope that explains why your site upgraded from 9.2.3 to 9.3.1 without receiving a notification for 9.3.0.

I received an alert: The Plugin “Woocommerce” needs an upgrade (9.2.3 ->9.3.1) – which clearly included the major update. – but that’s not the proper way of releasing a major update, concealed in the subsequent minor tweak.

If we spotted some issues during the canary release of a major update, we fix it immediately via a point release and then make that the stable version instead. I do realize that it could come across as concealing a minor tweak, but just wanted to point out the deeper reason behind the 9.2.3 to 9.3.1 jump.

• This reply was modified 6 months, 2 weeks ago by Rodel Calasagsag a11n.

Hi @wujek0. Try resetting your .htaccess file. It worked for some users having a similar issue, specifically here and here.

Hi @nicolasmierbach! There’s a known issue where the “Update WooCommerce Database”?button does not work on the WooCommerce home page. That same upgrade notice appears on other pages such as in WooCommerce > Orders, or WooCommerce > Settings. Please see if you could start the upgrade by clicking the “Update WooCommerce Database”?button there instead.

Thank you for the report @maginem. We are now working on a fix here.

Thanks for doing a compatibility check @josmoody, and for reaching out to the maintainers of the affecting plugin.

@jesperh95 I just want to ask if you were able to do a WooCommerce database update right after upgrading your WooCommerce version? The DB update seemed to have resolved this issue for some users.

We are investigating this further through this GitHub issue by the way.

Glad to know that you were able to resolve it through a database update, @boppar. We already have this on our radar by the way.

Hello @dimitrisv! Thanks for reporting this. We received a few other reports and we already have this issue on GitHub to start working on a fix. If the warning messages also appear on the store frontend, see if refreshing the page would effectively dismiss them.

Hi @cococat11 , WooCommerce 8.8.2 includes this PR which deprecates the $check_key_exists parameter.

We are already working on a fix for this issue. You can see the details and possible workarounds in our advisory here.

We are currently working on a fix to this issue. Please check here to see if the suggested workarounds will work for the meantime.

We published an advisory here to mention that this issue will be included in an upcoming fix. We also mentioned a few workarounds there that you can try. We are aiming to release a fix soon.

I saw those errors as well when I was trying to replicate the issue. We posted an update regarding this issue as well as possible workarounds here – https://developer.woo.com/2024/02/16/woocommerce-8-6-upcoming-fixes-checkout-page-product-page-and-compatibility-with-woo-subscriptions/. We aim to release a fix soon.

Just quickly mentioning here that we posted an advisory that suggested a few workarounds – ?https://developer.woo.com/2024/02/16/woocommerce-8-6-upcoming-fixes-checkout-page-product-page-and-compatibility-with-woo-subscriptions/

We received a few more reports. I started pointing them to the advisory we posted a few minutes ago to hopefully provide a workaround as we work on a fix which we plan to release soon – ?https://developer.woo.com/2024/02/16/woocommerce-8-6-upcoming-fixes-checkout-page-product-page-and-compatibility-with-woo-subscriptions/

We’re working on a fix here. There’s also an advisory that contains a workaround for the issue – https://developer.woo.com/2024/02/16/woocommerce-8-6-upcoming-fixes-checkout-page-product-page-and-compatibility-with-woo-subscriptions/