Support » Fixing WordPress » Response to 3.7 "definitive guide to disabling auto-updates"

  • Since I don’t have a way to respond to this thread…

    The definitive guide to disabling auto updates in WordPress 3.7

    I thought I’d chime in here…

    I’m a designer, not a developer, so I’m very concerned (AGAIN) about WP’s heavily “developer centric” approach and in this case it is once again something being forced on users (developers and designers) that they didn’t ask for and can’t (easily) get away from.

    At one point in the comments thread, the blog post author seems to think there isn’t even “one good reason” NOT to do auto-updates. Despite the fact that “auto-updates” have NEVER been available in the history of WP until, they are suddenly and irrevocably hard-coded into the framework.

    Well I’ll give you one good reason, in fact I’ll give you several:

    1. Because WP updates (can) jack up plug-ins – and no one ever knows which ones will be affected
    2. Because WP updates (can) jack-up themes – and no one ever knows which ones will be affected
    3. Because I want to initiate the conversation with my clients about updates AFTER I DO RESEARCH ON THE UPDATE and find out what problems (if any) others are having.
    4. The LAST THING I NEED is a rash of client calls SCREAMING AT ME because they’re website just went down do to an auto-matic update that I had NO idea was going to happen and no control over.

    I fully support “CentralGeek” in the comments of the link above: Sure, no problem, make auto-updates a part of the WP system. I agree that auto-updating is a great idea!!! JUST GIVE US A SIMPLE TICK-BOX OPTION OF DISABLING AUTO-UPDATES, or even better easily controlling what auto-updates we want enable.

    I suppose this request wont happen, and I’ll probably get slammed by people who write WP code instead of actually managing WP client sites. That’s typically what happens when I chime in with a perspective from the “dark side” of artsy-fartsy people.

    All this reminds me again of the old adage, “You know what progress is, right? It’s replacing what works with what seems like a good idea.”

    I support WP and the developers and thank them for creating an awesome open source website solution. But I do wish they were not so bull-headed sometimes…(I probably have the same problem…)

Viewing 2 replies - 1 through 2 (of 2 total)
  • Robin W

    (@robin-w) Moderator

    I too had/have reservations about auto update


    just adding the one line to your wp-config file allows you to have all the control over your updates ie

    # Disables all core updates:
    define( 'WP_AUTO_UPDATE_CORE', false );
    # Enables all core updates, including minor and major:
    define( 'WP_AUTO_UPDATE_CORE', true );
    # Enables core updates for minor releases (default):
    define( 'WP_AUTO_UPDATE_CORE', 'minor' );

    so you can easily switch it off.

    So if you don’t like it switch it off.

    For the moment I’ll run with them for my 6 sites, and trust the wp team when they say that the minor ones won’t break sites, but if the wp-team muck one up, they’ll ruin their own credibility – so guys make sure you don’t break our sites !

    Thanks RobinW – That sounds like a really easy, and very useful plug-in just waiting to be written 🙂

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Response to 3.7 "definitive guide to disabling auto-updates"’ is closed to new replies.