Update to 6.4 – Problematic DB Update

Yes, I plan to do is to take a fresh backup and of the malfunctioning site and move it to my dev environment (that works fine) in order to check if it will keep working or not (and go through the plugin deactivation chore in case that it doesnt work).

I will be obliged to get your ideas on the never ending scheduler migration.

Great! That sounds like a plan. Thank you for letting us know.

We’ll be here if you have more questions.

Hoping for a quick resolution.

Cheers.

Just to say that the quick resolution to this was to truncate all four tables vis-a-vis action scheduler (_actions, _claims, _groups, _logs) while disabling WP-Rocket’s plugin (that checks for cache expiration/CSS regeneration that was the bulk of the pending jobs etc.).

After this everything is going smoothly.

I was able to import the customers and orders in the reporting (that during the… lockdown ?? were not imported into reports) and now even the reporting is going fine.

I did this on my beta/dev environment (after the backup from production it too ceased to work and the action scheduler was… migrating).

Tonight (I am currently in GMT+2 timezone) I am going to apply the resolution to production.

I am looking forward to the exciting new developments with the separation of orders meta from the options meta, so that the solution will be even more robust.

My next project involves 150k products (with five attributes) and if all goes well, there is a project in line with 1.5 million records that I would like to experiment with on woo. I just hope that the new architecture for the linkage of the products with orders, will give ideas to the “hard” linkage of products with attributes for even faster performance when the number of products and/or attributes is enormous.

Once more, thank you for all your support and keep up the good work!

• This reply was modified 2 years, 7 months ago by dimitrisv.

Good news! Thanks for sharing what worked for you and hopefully it can work in exactly the same way on your production site.

If you have any further questions we recommend creating a new thread.

Have a good day!

Just to say that the news are not that… great.

I applied the solution to production. i.e. disabled wp_rocket (to not generate new tasks), truncated the data in the four tables and everything seemed find. All past jobs were run, I was able to import the past days new clients and orders in the reporting section etc.

Before re-enabling the wp rocket, I noticed the update for the 6.4.1 version and opted to update.

For the past couple of hours I am seeing the message “WooCommerce is updating product data in the background
Product display, sorting, and reports may not be accurate until this finishes. It will take a few minutes and this notice will disappear when complete”

When I go to see the details there are no details to be seen. Also there is no related pending task.

Also my server has minimal load, so it is not an issue of bottleneck. I actually think that it is not running the task.

Mind you, the whole issue here started after noticing that the “product attribute table regeneration” was failing (see: https://www.ads-software.com/support/topic/6-4-upgrade-product-attribute-lookup-table/)

Any guidance on how to properly debug the issue? (i.e. figuring out the actual status).

I think that was the core issue that I faced in the first place and if this job does not properly complete, then the regeneration of the product attributes table will fail and then the system/action scheduler will collapse once more…

I opened a new thread here

@dimitrisv No, do not do that. You have a problem and it is being worked on in this topic. Do not create duplicate topics, it makes it harder for all of the volunteers helping you. And yes, the Woocommerce people are volunteers too.

I have archived your new topic and your reply pointing to the new topic.

Cheers @jdembowski . I did opened a new one because 1. I have marked this as resolved (partly true) and 2. Because @rainfallnixfig suggested to do so.

Just to say in this thread that I opted to use this plugin https://www.ads-software.com/plugins/regenerate-product-lookup-table-for-woocommerce/ and run it manually and was able to generate both the lookup tables for products, and subsequently the product-attribute look up table.

The issue has been moved now on why this page is being called: wp-content\plugins\woocommerce\includes\admin\views\html-notice-regenerating-lookup-table.php

That gives the error about the product lookup table not being updated, while it was updated. Maybe it has not been fully updated and need to debug the product lookup table update function (residing here: wp-content\plugins\woocommerce\includes\wc-product-functions.php)

Hello @dimitrisv!

I understand you are facing issues with the product lookup table not being updated.

Please try regenerating this manually by going to WooCommerce > Status > Tools > Regenerate the product attributes lookup table.
Also, before running this out, I would suggest just having the WooCommerce plugin enabled to avoid any conflict with other extensions.

Screenshot:

Link to image: https://snipboard.io/3562V0.jpg

I am sorry for not making myself clear.

The issue remaining is this message here:

Link to image here:

The product lookup and the product-attributes lookup tables were regenerated with success, but this message remains.

• This reply was modified 2 years, 7 months ago by dimitrisv.

Hello,

The product lookup and the product-attributes lookup tables were regenerated with success, but this message remains.

Can you try clearing the WooCommerce transients? This would force a product data update. You can find that option in WooCommerce > Status > Tools > WooCommerce transients.

Let us know how it goes.

Thank you, I just did it again, the message remains.

Hi @dimitrisv! how’s it going?

Can you double-check if you have, by chance, disabled the WP-Cron on your site? If so, you’ll need to enable it again.

Also, if it’s enabled, can you try to purge all your cache and double-check with your hosting company if they’re not using any caching system on their side too?

Let us know how it goes!

We haven’t heard back from you in a while, so I’m marking this thread closed for now – we’ll be here if and/or when you are ready to continue.