[wp-hackers] Why no automatic database upgrade?
wp-hackers at thecodecave.com
Thu Jul 26 14:46:31 UTC 2012
I've had upgrades take 8 hour to process - and that was after hacking
the core to remove a step that would have made it take days. But this
is a rarer huge multisite install. As long as there is a constant that
can be defined to turn off the auto upgrade, this would be cool.
When I update the installs on my servers, its done by batch script
iterating the cpanel information. It then calls the upgrade screens via
On 7/26/2012 4:21 AM, Dion Hulse (dd32) wrote:
> On 26 July 2012 18:08, David Anderson <david at wordshell.net> wrote:
>> This then leads to the obvious question - why doesn't WordPress itself do
>> this automatically and not bother the user? I can save the user a click or
>> command - but is there some design reason why this is already an extra step?
>> Would I be in danger of optimising out a step that should not be optimised?
> It is actually done automatically for hte majority of users when they
> use the built in Core Upgrader, It's only those who are using SVN or
> manually updating who ever see the screen.
> There have been plans to skip the screen all together.. it's just a
> reasonably low priority change since it doesn't affect most users.
> However, In a position where WordPress is being used on the command
> line, performing the changes automatically might not be ideal -
> Although most changes are fast and are simply adding indexes or
> capabilities to roles, these upgrade routines in the past have been
> more intensive, and the task being run twice at the same time could
> *theoretically* cause problems.. but I honestly don't see that being a
> problem any time soon (But it could be).
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers