Update to 2.6.4 messed up things

  • Resolved madmax4ever

    (@madmax4ever)


    3 years, 2 months ago

    Hello,
    My site is currently running WordPress 5.8.1 and Woocommerce 5.6.0.
    define( 'WP_AUTO_UPDATE_CORE', false ); is set up in my wp-config.php file and I didn’t allow any plugin to auto-update.

    Nonetheless, I was notified yesterday morning by my system that WooCommerce Admin updated automatically from 2.6.2 to 2.6.4.
    It’s the first time in two years that I get such a behavior from a plugin!
    I could have been OK with it as it’s mentionned 2.6.4 is a security release, even if I prefer testing updates on a staging site before upgrading live.

    And here is the problem:

    From this switch, Woocommerce (still in 5.6.0, not updated to 5.7.0, I precise this!) in the dashbord widget ask me to complete setup! It claims I’m in Step 4 of 6!

    I tried to revert to v2.6.2 on my staging site, but nothing better! The parameters v2.6.4 modified (deleted?) aren’t back…

    I add that I installed the brand new v2.6.5 on my staging site, hoping to get a fix, but no.

    Could you check that please?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter madmax4ever

    (@madmax4ever)

    My bad, in fact, 2.6.5 fixed things.
    Weither the plugin deactivated itself after update or I just forgot to finally activate it at the end of my tests…

    Thank you for that.

    Hope my testimony helps others.

    As a final word, I’ve now added add_filter( 'auto_update_plugin', '__return_false' ); to my system, just to be sure to get hands on things and avoid plugins and themes to allow themself to auto-update, even though they weren’t allowed in the first place…!

    • This reply was modified 3 years, 2 months ago by madmax4ever.
    Plugin Support darcie

    (@darciemg)

    Hi @madmax4ever,

    Thanks for your feedback and for letting us know that 2.6.5 resolved your issues. Appreciate the update on this! It should help others as well. ??

    All the best.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Update to 2.6.4 messed up things’ is closed to new replies.