WooCommerce database upgrades

  • Resolved Matt Lowe

    (@squelch)


    4 months, 3 weeks ago

    I’ve been having endless problems with WooCommerce upgrades for the last few years, where WC constantly wants to update the database and yet no matter how many times I go through the update process it always wants to update it again immediately after the upgrade has completed. Only today did it occur to me to try disabling APCu Manager to see if there was a link, and indeed there was: as soon as APCu Manager was disabled I got the “thanks for updating” message and the WooCommerce database version matched the WooCommerce version as expected.

    I’m not sure whether this counts as an APCu Manager problem or a WooCommerce problem. Clearly the object cache needs to be cleared as part of the WC DB upgrade process. But is that something WooCommerce need to implement on their side, or is it something that APCu Manager needs to detect and automatically flush on its side?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Pierre Lannoy

    (@pierrelannoy)

    I’m definitely sure it’s a work for WooCommerce. They have to flush their cache whenever it’s needed, and they’re the only ones who know when it’s necessary.

    Note (and you can try it) it will be exactly the same behavior with other object cache plugins (like plugins for Redis or Memcached).

    Thread Starter Matt Lowe

    (@squelch)

    @pierrelannoy Yeah I’d come to the same conclusion. I did use the Redis cache for a little while but after a catastrophic data corruption incident on a customer database I switched away from it again. We’ve never seen any issues like that with the APCu Manager plugin, so it’s our preferred object cache plugin. But when we were using the Redis Cache plugin I don’t remember WooCommerce database upgrades being any smoother, and as you say WooCommerce really should really be flushing the cache after upgrading the database. That’s clearly solely their responsibility.

    The problem is trying to get WooCommerce to listen to anyone other than their core developers!

    Thanks for the reply, I’m marking this as resolved.

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