Title: Automatic Updates Last modified: August 31, 2016 --- # Automatic Updates * Resolved [timetraveler4309](https://wordpress.org/support/users/timetraveler4309/) * (@timetraveler4309) * [10 years, 1 month ago](https://wordpress.org/support/topic/automatic-updates-7/) * To the developers at WordPress. * First thank you for the ongoing work that you do. * Today, however, I need to address an issue that is glaring: automatic updates without an option to disable such. * In theory, auto updates seem like a good idea, but in reality this practice can be very disruptive. * We have been waiting to update WordPress until a few issues were addressed within the program. This morning to my surprise WordPress updated automatically. In doing so it created confusion for one of my clients as the image of the product disappeared from the site. Exploring the situation, I also found other problems the update caused on the site. * Updates can be beneficial, but they can also have a negative impact – one that can be difficult to recover from. Let’s face it, you can not walk into any business/ store and remove or rearrange the products. Access and ability to alter any site should never be a default, especially if it can effect a business, even unintentionally. My site is protected by firewalls and security for a reason; action(s) that can impact the site are addressed as such. * There was a backup within the site, but that has also been auto updated, as well as the copy on a local host when that was loaded. (I am now aware that one can alter the wp-config file to disable auto updates, but that’s too little to late). * I STRONGLY urge the developers at WordPress to consider an option/choice to disable automatic updates. * Thank you for you time and consideration of this issue. Sincerely, Robert Viewing 9 replies - 1 through 9 (of 9 total) * Moderator [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [10 years, 1 month ago](https://wordpress.org/support/topic/automatic-updates-7/#post-7356716) * First, a quick point of clarification. Minor updates (4.5 to 4.5.1, 4.5.1 to 4.5.2, etc) are automated by default as they often contain security fixes. Major updates (4.3 to 4.4, 4.4 to 4.5, etc) are not automated unless such automation is provided by a plugin or your hosting provider, and many hosting provider do by default (we have no control over that). * At the WordPress level, you can disable automated updated following this guide: [https://codex.wordpress.org/Configuring_Automatic_Background_Updates#Configuration_via_wp-config.php](https://codex.wordpress.org/Configuring_Automatic_Background_Updates#Configuration_via_wp-config.php)( again though, that won’t affect automated updates provided by your hosting provider) * Thread Starter [timetraveler4309](https://wordpress.org/support/users/timetraveler4309/) * (@timetraveler4309) * [10 years, 1 month ago](https://wordpress.org/support/topic/automatic-updates-7/#post-7356718) * Hi James, Appreciate the fast reply and clarification. Whether they are major or minor updates,if they effect a site and it’s business then it should be in the hands of the owner. * All due respect. Sincerely, Robert * Moderator [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [10 years, 1 month ago](https://wordpress.org/support/topic/automatic-updates-7/#post-7356720) * Sure thing, that’s why we have the constant available to configure in wp-config. php: [https://codex.wordpress.org/Configuring_Automatic_Background_Updates#Configuration_via_wp-config.php](https://codex.wordpress.org/Configuring_Automatic_Background_Updates#Configuration_via_wp-config.php) * Just keep a close eye on [https://wordpress.org/news/](https://wordpress.org/news/) as many minor updates are security updates: [https://wordpress.org/news/category/security/](https://wordpress.org/news/category/security/)( once they’re publicly announced, they can be reverse-engineered by folks of malicious intent) * If your hosting provider is the one forcing the updates though (again, many do by default these days), you’ll need to bring that up with them, we have no control over that. * Thread Starter [timetraveler4309](https://wordpress.org/support/users/timetraveler4309/) * (@timetraveler4309) * [10 years, 1 month ago](https://wordpress.org/support/topic/automatic-updates-7/#post-7356723) * Hi James, Yes – the wp-config. I now know this, but as stated in the initial post “too little to late”; we were not ready for this issue today. * I do appreciate what the developers at WordPress have accomplished – it’s amazing! * That said, few businesses would expect an update, that could adversely effect it’s site, without an advanced notice and approval from various departments. We thought we had a backup plan but that was updated as well… * So, moving forward and back to topic, PLEASE consider an option of disabling “ auto upgrade” within the program itself. * Thanks, Jan * [Andrew Nevins](https://wordpress.org/support/users/anevins/) * (@anevins) * WCLDN 2018 Contributor | Volunteer support * [10 years, 1 month ago](https://wordpress.org/support/topic/automatic-updates-7/#post-7356796) * You can use a plugin of course * Thread Starter [timetraveler4309](https://wordpress.org/support/users/timetraveler4309/) * (@timetraveler4309) * [10 years, 1 month ago](https://wordpress.org/support/topic/automatic-updates-7/#post-7356834) * Hi Andrew, Thank you for the response. * Plugins are an option, but they can create other conflicts. * As my associate Jan stated above, we are aware of adding a code to the wp-config file and have done so. * But, whether a code or a plugin, it seems like a back-end solution to something that could easily be addressed in the front-end. * Searching the web, I have found many WordPress customers/users that have had issues due to untimely or unwanted updates. It also seems that the vast majority had no idea about adding a code to the wp-config file. * With respect – since this is a request/feedback page, we are not really looking for a technical work around. This post was opened to highlight, something that caused a major problem for us with a client, and to further suggest a solution that respects the owner of the site – a simple option to allow/deny auto updates. * Thank you, Robert * [mitchberry](https://wordpress.org/support/users/mitchberry/) * (@mitchberry) * [9 years, 10 months ago](https://wordpress.org/support/topic/automatic-updates-7/#post-7356997) * yeah, i’m glad i found this. I had a similar thought. I HAVE to change a bunch of core files to get what i’m doing, to work. there is no way around it. Then i found a post where James said “DO NOT alter core files. use a plugin” and the guy said “it won’t do what i need” etc…. and there was debate about auto updating overwiting core files, so i went to look for a way to disable that, and found a post where someone said ” YOU DESTROYED MY FREAKIN BUSINESS AND THOUSANDS OF HOURS OF WORK!!!!!!” in a more tactful way. so yeah…. This is an issue i will be facing too, i’m just glad i found this. I don’t want to have to make daily backups of my entire site and have down time every few weeks or months just to undo any updates that come up, only do have to do it again and again and again. I wish we could BLOCK the WP home ip altogether with a firewall, or disable communication completely. I COMPLETELY understand why it’s there. But.. I’m with Time Traveler. I’m one of the few people who needs for this NOT to be a thing and wish it were an option to turn off. If i remember correctly, i think that previous versions of WP DID in fact have a “turn auto updates off” ticker in settings. not sure why it disappeared. I would love to have the OPTION without having to install YET ANOTHER plugin… i have so many plugins, there are more plugin files than core files at this point! and… i agree. they can cause all sorts of conflicts, and in order to get the plugins to do -EXACTLY- what i need them to do, i must without a doubt, absolutely, positively, change core files! However, this little revelation leads me to understand WHY the plugins only do 90% of what i need. * I was griping to my girlfriend last night “YOU CAN’T POSSIBLY TELL ME… that NO ONE!!… NO ONE IN THE ENTIRE WORLD!!! NEEDS THIS FUNCTIONALITY??? WHY ISN’T IT WRITTEN IN!!!!??????” well now i know…… because it will be wiped away every time there’s an update lol.. even minor ones can and do cause conflicts, IF the file that’s being updated is one that you previously altered. * crruuuuuuuddddddddddddddddd …. well, thanks… * Moderator [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [9 years, 10 months ago](https://wordpress.org/support/topic/automatic-updates-7/#post-7356998) * Just making sure you didn’t miss [https://wordpress.org/support/topic/automatic-updates-7?replies=8#post-8373714](https://wordpress.org/support/topic/automatic-updates-7?replies=8#post-8373714) * It’s not a nifty checkbox, but the functionality is built-in. * [debbitage](https://wordpress.org/support/users/debbitage/) * (@debbitage) * [9 years, 4 months ago](https://wordpress.org/support/topic/automatic-updates-7/#post-8703462) * It should be a nifty checkbox, though, and in plain sight in the settings where normal people can come across it, instead of learning about it after it happens. On by default is not always a good thing, no matter how little you think of your users. Viewing 9 replies - 1 through 9 (of 9 total) The topic ‘Automatic Updates’ is closed to new replies. ## Tags * [auto](https://wordpress.org/support/topic-tag/auto/) * [automatic](https://wordpress.org/support/topic-tag/automatic/) * [choice](https://wordpress.org/support/topic-tag/choice/) * [option](https://wordpress.org/support/topic-tag/option/) * [Updates](https://wordpress.org/support/topic-tag/updates/) * [upgrade](https://wordpress.org/support/topic-tag/upgrade/) * In: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/) * 9 replies * 5 participants * Last reply from: [debbitage](https://wordpress.org/support/users/debbitage/) * Last activity: [9 years, 4 months ago](https://wordpress.org/support/topic/automatic-updates-7/#post-8703462) * Status: resolved ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics