[wp-hackers] WP 3.7 auto-update
otto at ottodestruct.com
Fri Oct 11 15:56:55 UTC 2013
On Fri, Oct 11, 2013 at 10:32 AM, Mika A Epstein <ipstenu at ipstenu.org> wrote:
> And we'll put that in the OMGWTFBBQ post, and I'm SURE Nacin'll have it in
> the Press Release on .org :)
> And I'm sure we'll have people scream.
Note that for the majority of cases where users would legitimately
need it to be turned off, it is turned off automatically.
- If the setup is such that the user must put in FTP credentials or similar,
- If there are .svn or .git directories, indicating the user has a
deployment system for the site,
- If getting files via SSL doesn't work for whatever reason, so it
can't download securely,
- If wp-cron is buggered for whatever reason and the updater doesn't fire,
- If file modification has been manually disabled with
DISALLOW_FILE_MODS being defined,
Any of these will cause it to disable the auto-updater. Turning it off
manually should be a relatively rare operation, for those people with
special cases or needs.
If they do want to turn it off, then there's a few good ways:
1. define ('AUTOMATIC_UPDATER_DISABLED', true); - This is a blunt
instrument. It simply disables the core automatic upgrader code at the
root. Overrides everything.
2. WP_AUTO_UPDATE_CORE can be defined instead to allow more fine
grained control. Set it to one of these:
- false = no updates
- true = ALL updates
- minor = Minor releases only
Using this essentially sets the default values for the following
filters. Using these following filters will allow you to override this
3. Filters exist to allow you to allow specific kinds of updates as well:
allow_dev_auto_core_updates - if you're on a development version, and
this filter gets returned a true value, then it will enable dev/beta
allow_major_auto_core_updates - Pretty much what it says on the box.
Return true to allow each of these, false to disallow them.
More information about the wp-hackers