[wp-trac] [WordPress Trac] #13796: Upgrade script should set a flag for pre-existing .maintenance file

[WordPress Trac]

#13796: Upgrade script should set a flag for pre-existing .maintenance file
-------------------------+--------------------------------------------------
 Reporter:  dndrnkrd     |       Owner:             
     Type:  enhancement  |      Status:  new        
 Priority:  normal       |   Milestone:  2.9.3      
Component:  General      |     Version:             
 Severity:  normal       |    Keywords:  maintenance
-------------------------+--------------------------------------------------
 It's possible (and prevalent) to use .maintenance with logged-in logic as
 a lockout for a site that's in development. It should be possible to run
 an auto upgrade of both core and plugins without having an in-development
 site leaked out to the public. Simply, if a .maintenance file exists in
 the site root, it should be renamed .maintenance_{nonce} or similar and
 restored once the upgrade is complete, rather than simply overwriting and
 deleting.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/13796>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software