20 Comments

  1. Knut Sparhell

    Minor updates hardly break sites and 3.8.2 did not. One kind of security updates is hardening. A hardening may break functionality in some cases. Fixing a regression fast and smoothly as also one of the reasons auto updates is beneficial.

    One of the arguments for not wanting auto updates is that when doing a manual update you can test your site and eventually and immediately revert or fix any breakage. Not many would immediately discover that Quick Draft was broken. This would only be discovered when someone actually tried to use it. In the mean time you would have manually updated all your sites, this being an important security update. Only allowing manual updates would not have made a real difference.

    The decision not to include a UI for turning off automatic minor updates is still wise. Finding a plugin for exposing this option, or a code snippet to disable it blindly, is easy.

    Report

  2. azpir8king

    Well, 3.8.3 automatically updated at 9:03 PM and 1 hour later, All of my sites went over SQL usage and now all three of my sites are down. I will spend HOURS sorting this out. Auto updating SUCKS. Leave us the choice so we can update ONE site…if it crashes, we know NOT to update the others until we resolve the problem. Stupid way to release an update for WordPress.

    Report

    • Knut Sparhell

      You do have a choice. If you are maintaining a lot of sites I’m sure you know how. I use the Advanced Automatic updates plugin, all options on, on all sites. Never had a site broken.

      Report

    • Jeff Chandler

      I suggest installing a plugin that allows you to control the automatic update behavior so it only updates the site when you want it do.

      Report

  3. Keith Davis

    “On a brighter note, WordPress 3.9 is expected to ship later this week.”
    Maybe the Quick Draft fix could have waited until then?

    Report

  4. idogenealogy2013

    On two of my sites the auto update to 3.8.3 went fine. But on one the auto did not work THIS time. It did with no problems for 3.8.2. When I did.the upgrade myself, I got several errors which I could NOT capture. The upgrade was “successful” although I’m getting errors for “upgrade.php” when I update plugins. Three plugins installed successfully despite these errors:

    Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /……………../update.php on line 120

    Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /……………../update.php on line 272

    Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /……………../update.php on line 417

    Yes — I’m turning this into my host for this site — but never seen anything like this before.

    Report

  5. conhost

    I just discovered it broke one of my sites. I can get to dashboard but any other selection in admin panel just stalls out. I have no idea at this moment exactly how many sites are screwed up but if I have to go to the server to fix each one…this will take me DAYS! Autoupdate was a stupid idea.

    Report

Comments are closed.

%d bloggers like this: