Title: Adding a flag for automatic updates when source code control detected? Last modified: August 21, 2016 --- # Adding a flag for automatic updates when source code control detected? * Resolved [Brian Hogg](https://wordpress.org/support/users/brianhogg/) * (@brianhogg) * [12 years, 6 months ago](https://wordpress.org/support/topic/adding-a-flag-for-automatic-updates-when-source-code-control-detected/) * As noted in Nacin’s post: * > [The definitive guide to disabling auto updates in WordPress 3.7](https://make.wordpress.org/core/2013/10/25/the-definitive-guide-to-disabling-auto-updates-in-wordpress-3-7/) * If there are any source code control systems detected in the WP folder or anywhere up the tree, the automatic updates do not fire. This can be enabled via the “ automatic_updates_is_vcs_checkout” filter. Thoughts on adding this as an option( ie. “Enable Automatic Updates if Source Code Control Present”)? * [http://wordpress.org/plugins/update-control/](http://wordpress.org/plugins/update-control/) Viewing 10 replies - 1 through 10 (of 10 total) * Plugin Author [Chip Bennett](https://wordpress.org/support/users/chipbennett/) * (@chipbennett) * [12 years, 6 months ago](https://wordpress.org/support/topic/adding-a-flag-for-automatic-updates-when-source-code-control-detected/#post-4267835) * I’ve thought about it – along with the debug email filter. * But if someone is running from VCS, are they likely even to bother with this Plugin, rather than just rolling their own `add_filter()` calls? * Thread Starter [Brian Hogg](https://wordpress.org/support/users/brianhogg/) * (@brianhogg) * [12 years, 6 months ago](https://wordpress.org/support/topic/adding-a-flag-for-automatic-updates-when-source-code-control-detected/#post-4267842) * I am at least 🙂 * I was thinking that, and even though I could just throw it into the theme I’d rather just keep it all to a plugin like this one. It might be good for those that have source code control up the folder tree and don’t realize that stops the auto update from happening, to see the option. Perhaps at the bottom and with a short one-line explanation. * Plugin Author [Chip Bennett](https://wordpress.org/support/users/chipbennett/) * (@chipbennett) * [12 years, 6 months ago](https://wordpress.org/support/topic/adding-a-flag-for-automatic-updates-when-source-code-control-detected/#post-4267844) * > I am at least 🙂 * I thought that might be the case. 🙂 * Let me think about how best to add it. * Plugin Author [Chip Bennett](https://wordpress.org/support/users/chipbennett/) * (@chipbennett) * [12 years, 6 months ago](https://wordpress.org/support/topic/adding-a-flag-for-automatic-updates-when-source-code-control-detected/#post-4267922) * Okay, I just pushed version 1.2, which adds a toggle for advanced options, and introduces options to disable the VCS check, and to enable the debug email. * Thread Starter [Brian Hogg](https://wordpress.org/support/users/brianhogg/) * (@brianhogg) * [12 years, 6 months ago](https://wordpress.org/support/topic/adding-a-flag-for-automatic-updates-when-source-code-control-detected/#post-4267923) * Thanks! Nice way to display those options. * After I save the options, it flips back to ‘No’ for configure advanced options, is that intentional? It does seem to save the options so that’s good, just feels like it should continue to display those options if Yes is selected. If no is selected it would keep the settings as the default. * Regardless thanks again for such a quick response. * Plugin Author [Chip Bennett](https://wordpress.org/support/users/chipbennett/) * (@chipbennett) * [12 years, 6 months ago](https://wordpress.org/support/topic/adding-a-flag-for-automatic-updates-when-source-code-control-detected/#post-4267929) * It’s intentional. I’m trying to keep the UI as simple/uncluttered as possible. I’m not a UI person, so I ran with the “Chrome” model for automatic updates. In Chrome, “advanced settings” are always hidden, unless you click the link. So, I’m trying the same thing here. * It’s all experimental; I could change it if it becomes too tedious. * Thread Starter [Brian Hogg](https://wordpress.org/support/users/brianhogg/) * (@brianhogg) * [12 years, 6 months ago](https://wordpress.org/support/topic/adding-a-flag-for-automatic-updates-when-source-code-control-detected/#post-4267931) * I’d almost change the show/hide to a link rather than a dropdown, just because having it hidden with ‘configure’ set to ‘no’ seems to imply that the advanced options have no effect when no is selected, at first glance. * I’m sure there are arguments either way and I’m not a UI expert by any means, it just threw me off at first. * Thanks again! * Plugin Author [Chip Bennett](https://wordpress.org/support/users/chipbennett/) * (@chipbennett) * [12 years, 6 months ago](https://wordpress.org/support/topic/adding-a-flag-for-automatic-updates-when-source-code-control-detected/#post-4267932) * What about renaming as “Advanced Settings”, and change the dropdown to “Show” and “Hide”? * Thread Starter [Brian Hogg](https://wordpress.org/support/users/brianhogg/) * (@brianhogg) * [12 years, 6 months ago](https://wordpress.org/support/topic/adding-a-flag-for-automatic-updates-when-source-code-control-detected/#post-4267937) * Still feels like a show/hide link to me rather than dropdown (similar to Chrome’s“ Show advanced settings…” link), but “Advanced Settings” and Show/Hide would definitely be clearer IMO. * Plugin Author [Chip Bennett](https://wordpress.org/support/users/chipbennett/) * (@chipbennett) * [12 years, 6 months ago](https://wordpress.org/support/topic/adding-a-flag-for-automatic-updates-when-source-code-control-detected/#post-4267938) * Awesome. We’ll give that a spin! Viewing 10 replies - 1 through 10 (of 10 total) The topic ‘Adding a flag for automatic updates when source code control detected?’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/update-control.svg) * [Update Control](https://wordpress.org/plugins/update-control/) * [Frequently Asked Questions](https://wordpress.org/plugins/update-control/#faq) * [Support Threads](https://wordpress.org/support/plugin/update-control/) * [Active Topics](https://wordpress.org/support/plugin/update-control/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/update-control/unresolved/) * [Reviews](https://wordpress.org/support/plugin/update-control/reviews/) * 10 replies * 2 participants * Last reply from: [Chip Bennett](https://wordpress.org/support/users/chipbennett/) * Last activity: [12 years, 6 months ago](https://wordpress.org/support/topic/adding-a-flag-for-automatic-updates-when-source-code-control-detected/#post-4267938) * Status: resolved