WordPress 3.7 & Auto Updates

Community Forums Forums General Discussion WordPress 3.7 & Auto Updates

This topic is: not resolved

This topic contains 7 replies, has 6 voices, and was last updated by  Summer 1 year, 1 month ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #69281

    Lisa at OG
    Participant
    Post count: 119

    It appears that WordPress 3.7 is set up to auto update to new versions of WordPress when they are released rather than allowing users to be prompted and update manually when ready. In the case of the latest NextGen fiasco this would have been catastrophic for most of our client sites given that it would have broken the site. If you wish to turn OFF auto updates of new WordPress versions (and do them manually instead) you can add the following code to your functions.php:

    add_filter ( ‘allow_minor_auto_core_updates’, ‘__returnfalse’ );

    We found this info at http://codex.wordpress.org/Configuring_Automatic_Background_Updates. As far as I can tell you will still receive a notification when new WordPress updates become available.

    Does anyone know if this is correct?

    #69283

    RobG
    Participant
    Post count: 1055

    Hi Lisa I did not get any auto update for 3.7 I just took it my self so I’m not sure who is reveiving this auto update.


    To speed up the process please post the link to the website in question.

    We recommend using Firebug to view source codes http://getfirebug.com/

    RobGoss WordPress Developer
    We build WordPress websites for your business or personal goals
    http://www.robgoss.com / Follow me Twitter / https://twitter.com/robgoss

    #69290

    Summer
    Participant
    Post count: 1123

    Rob, you won’t start receiving auto-updates of minor versions of WordPress plus plugins and themes until after you upgrade to WP to 3.7.

    After that, everyone will be auto-updating. But if ever you don’t want something to auto-update without your express involvement, you’d have to disable the feature.

    And I don’t think they’d turn off the notifications… otherwise how would people know what needs to be updated? For that matter, is there now a log that lets you know when something was auto-updated? I think that would be necessary info for most admins.


    #69296

    RobG
    Participant
    Post count: 1055

    Hi Summer thanks for letting me know I think is a good thing becase it will allow most WordPress website to keep everything updated.


    To speed up the process please post the link to the website in question.

    We recommend using Firebug to view source codes http://getfirebug.com/

    RobGoss WordPress Developer
    We build WordPress websites for your business or personal goals
    http://www.robgoss.com / Follow me Twitter / https://twitter.com/robgoss

    #71112

    jmrallen
    Participant
    Post count: 59

    Is there any sort of consensus as to whether disabling minor auto-updates is a good thing? I would hate to think a website was cruising along just fine until an auto-update bricked a plugin or something without the development community having time to anticipate and code for it. Would folks recommend implementing this little bit of code in the functions.php file just to be safe?

    #71142

    emasai
    Participant
    Post count: 790

    I’m interested in the answer to jmrallen’s question too.


    Need Website Customization or a Responsive CSS fix? Contact Me
    Lynne emasai.com

    #71173

    Victor Font
    Participant
    Post count: 74

    I disabled all core updates by adding the following to my wp-config file:

    # Disables all core updates:
    define( ‘WP_AUTO_UPDATE_CORE’, false );

    #71184

    Summer
    Participant
    Post count: 1123

    I plan to disable auto-updates across the board, core and plugins. I will re-evaluate after the system has had a one year shakedown cruise. :)

    I’m just more than a little leery about this. I mean, I ran into problems updating two sites from 3.6 to 3.6.1 with plugin behaviors failing, and am still dealing with minor tweaks from a couple 3.6.1 and Genesis 2.0 upgrades as well. No one can predict that future plugin chokes won’t happen with a silent background update from 3.7.2 to 3.7.3 or what have you. Shoot, I still get failures now and again when clicking the “update now” button for plugin notices, and it took me until 2012 to even start using that on a regular basis (have never used it for core update… bitten once too often).

    Unless you’re on a site running nothing but Automattic authored plugins, I don’t see an advantage being an early adopter for this process, unless you’re actively helping them test the system and crush the bugs.


Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.