WooCommerce database update required WooCommerce has been updated! [CONTINUES]

Hi @damelco,

The WooCommerce wc_update_340_state function is defined in /includes/wc-update-functions.php.

https://github.com/woocommerce/woocommerce/blob/b18e2437f482bbc05a2da49ef89221fd373d140a/plugins/woocommerce/includes/wc-update-functions.php#L1744

It seems there was a similar behavior on a few sites a while back, due to the update scripts not setting up all the required database tables. But this was fixed long ago.

Once the WooCommerce update is done, can you head to WooCommerce > Status > Tools, regenerate product lookup tables and verify base database tables on that page?

Link to images:
https://d.pr/i/PQiztW
https://snipboard.io/OXcbBN.jpg

It may take a few minutes to complete. If this doesn’t help either it means that there’s a wider problem with Action Scheduler or WP-Cron in general, so you might want to use WP Crontrol plugin as suggested above.

Cheers.

BEFORE REGENERATE:
Database verified successfully.
REGENERATE:
Lookup tables are regenerating
SA – wc_update_product_lookup_tables_column (x11)
SA – wc_update_product_lookup_tables_rating_count_batch (x2)
AFTER REGENERATE:
Database verified successfully.

no effect on issue at all.

additionally, I have not been able to trigger the WooCommerce database version reversion to 3.1.0 by manually running any CRON event with WP_Control.

-DJ

Hi @damelco

Can you double-check if you have any caching software running?

Also, by default, the object cache is non-persistent. This means that data stored in the cache resides in memory only and only for the duration of the request, but sometimes there’s some caching system on the server-side too that affects the cache and also the object_cache.php file. I’d recommend checking out with your hosting company for a double-check.

Let us know how it goes!

My very best,

no caching … other than the mention of caching routines with WC (which I did already try using the WC-tools to address).

-DJ

Hey @damelco,

Can you reach out to your web host to check this further?

Your host has access to the server logs and those may be helpful to understand why your database version reverts to 3.1.0.

Thanks!