WordPress.org

Support

Support » Requests and Feedback » [Resolved] Why Auto-Updates are a Bad Idea

[Resolved] Why Auto-Updates are a Bad Idea

Viewing 9 replies - 1 through 9 (of 9 total)
  • Moderator James Huff

    @macmanx

    Support Team Rep.

    That really doesn’t have anything to do with auto-updates, that simply means your database server is offline. It’s not even a WordPress-specific issue and can happen to anyone at any time (especially on not-so-great hosting providers).

    Double-check your database connection details in your wp-config.php file. If they’re correct, you’ll need to contact your hosting provider to reboot your database server and find out why it went offline.

    When an update doesn’t WORK properly it can cause this.

    In this case, the site was working fine. I got an email that my site had auto-updated and, bam, site down.

    There is a reason we’re told to back up before updating – because sometimes things flake out upon upgrade.

    Moderator James Huff

    @macmanx

    Support Team Rep.

    When an update doesn’t WORK properly it can cause this.

    Not entirely, it’s more often the other way around. An update cannot take a database server offline (unless the server is incredibly unstable and can’t handle a few simple queries), but having a database server offline can cause the update to fail. Did you check your site before receiving the email, or did you only check it after the email and see the problem?

    Yes, I’d already viewed the site earlier in the day. An update doesn’t take the server offline, but it can confuse the settings and then it doesn’t know what it’s connecting to.

    (I’ve seen an update fail and cause this problem before – it’s just that I was in the driver seat then; it wasn’t sprung on me. I’ve also seen dozens and dozens of updates work just fine (I’ve just had five other sites auto-update, and they all went smoothly), but this can happen. It’s why we need to be able to choose when our sites do and don’t update so we can be sure that a) our backups are completely current and b) it’s an okay time for handling any “oopses” that occur.

    Moderator James Huff

    @macmanx

    Support Team Rep.

    An update doesn’t take the server offline, but it can confuse the settings and then it doesn’t know what it’s connecting to.

    Not really, no. The only connection details that WordPress uses are in the wp-config.php file, and a WordPress update will never replace, delete, or modify the wp-config.php file.

    Moderator James Huff

    @macmanx

    Support Team Rep.

    To clarify, I agree that a setting would be nice, I’m just pointing out that it is incredibly unlikely that an update took your database server offline.

    Moderator James Huff

    @macmanx

    Support Team Rep.

    I had not seen that whole page, no. (A little piece of it, I think, but not that much information.) Thanks!

    Moderator James Huff

    @macmanx

    Support Team Rep.

    You’re welcome!

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘[Resolved] Why Auto-Updates are a Bad Idea’ is closed to new replies.