12 Comments

  1. Marcus Tibesar
    · Reply

    WordPress 5.6 delays, issues around auto-updates, jquery, meta boxes, block-based widgets, and navigation screen. Oh my!

    Report

  2. Miroslav Glavic
    · Reply

    There are tons of plugins that deal with auto-updates. The latest round gives the option for plugins and themes, not for core. All three should be optional.

    I use this plugin: https://imgur.com/HGGGbpK

    Here are the options, quite simple: https://imgur.com/cZIzMCB

    What if an update done by the auto-update screws up the site?. Manual updates, I am right there to fix things if things break up, screw up, F*** up.

    Forced auto-updates are so wrong.

    To reply to some of the replies to my post here……….yes I know some people have clients, updating 100 sites take so long……..well, your clients pay you to keep things up to date (maintenance), update the sites manually. You shouldn’t be charging your clients if you turn on auto-updates, you aren’t updating/maintain if you do.

    I update close to 385 sites for my clients. I get paid to do that, so I do it. Part of maintenance is to make sure the site does not screw up.

    Report

  3. Denis
    · Reply

    They need to create a user friendly UI for the automatic plugin updates like toggles. Currently it’s hard to distinguish where it is activated and where it’s not.

    Report

  4. Ricardo
    · Reply

    Security is essential in any site.
    WP (30% of them) has an additional responsibility on that matter.

    Wouldn’t a core backup system resolve the big issue – breaking sites?

    A “simple” rollback one. Just some snapshots of plugins, themes, WP versions in a before/after update state?
    And even a way to automatically detect if the site is down, rollback and warn the developer?

    Report

  5. Rory Silva
    · Reply

    One of my plug-ins crashed my site after an update.

    I restored the site to a backup from a few days ago and before I could do anything it auto-updated to the buggy plug-in and crashed again.

    I was stuck in this loop until I went back far enough to where I hadn’t set my auto updates on.

    No more auto updates for me. Thanks.

    Report

  6. David Anderson
    · Reply

    Will automatic updates still occur even if your installed plugins aren’t indicating they’re tested with the update?

    I’m thinking of what’s going to happen when you have a combination of things like 1) old plugins, 2) new WordPress versions that have updated jQuery, and 3) auto-updates enabled…. that sounds like a recipe for automated site failure.

    Report

    • Justin Tadlock
      · Reply

      These are all very good questions. I’ll see if I can find out or get someone with more knowledge of this to respond.

      Report

    • Jb Audras
      · Reply

      Hi David,

      No, it doesn’t work that way. The “Tested up to” field is here to indicate on which maximum version of WP the plugin has been tested and this information is used to display a message indicating that the plugin has not been tested on this version of WordPress in the plugin installation screen, but that’s all. This is not used to actively prevent the installation of the plugin.

      Worth noting that the only actively and officially supported version of WordPress being the latest version released, there is currently nothing preventing the installation of a plugin that does not indicate that it has been tested with the current version.

      Have a look on the plugin installation screen, and scroll through the plugins list: there is a message to show if the plugin was tested or not with the current version of WP (= “Untested with your version of WordPress” for example), but you can always install it if you want to.

      Report

      • David Anderson
        · Reply

        Confusing response – starts with “No”, but appears to go on to explain that the answer is “Yes” (users with old plugins will get automated site failure if they opt-in to automated core upgrades, notwithstanding the information being available to prevent it).

        Report

  7. Ryan
    · Reply

    From a security and software development standpoint changes to a production environment should go through a testing and change management procedure. I’ve personally had far too many plugins and WP update wreck my site to allow auto updates (not to mention how many Windows updates have bricked computers over the years). I’ve disabled them all (core, plugins, themes) and now have a set update schedule that follows a system-wide backup.

    Report

  8. Matija
    · Reply

    Auto update feature seems way to risky to me without an auto restore / rollback feature in case of failure. I wouldn’t like to wake up one morning to a dozen of crashed sites and angry emails from clients.

    Report

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: