[wp-trac] [WordPress Trac] #13988: No Obvious Way to End Maitenance Mode / Problems Upgrading Large Plugins on 1and1

[WordPress Trac]

#13988: No Obvious Way to End Maitenance Mode / Problems Upgrading Large Plugins on
1and1
-----------------------------+----------------------------------------------
 Reporter:  layotte          |       Owner:                                   
     Type:  defect (bug)     |      Status:  new                              
 Priority:  normal           |   Milestone:  Unassigned                       
Component:  Upgrade/Install  |     Version:  3.0                              
 Severity:  normal           |    Keywords:  maitenance mode, plugins, upgrade
-----------------------------+----------------------------------------------

Comment(by dd32):

 > 1) The admin should not be restricted from browsing the site/wp-admin in
 "Maintenance Mode"

 The admin is just as likely to break during a plugin/core upgrade as any
 other page

 > 2) The admin should be able to cancel "Maintenance Mode" (or if there is
 a way, it should be obvious)

 > 3) The auto-upgrade/maintenance mode needs to die gracefully when an
 error occurs, such as a memory_limit is reached.

 Which is impossible to track, At the point that execution stops due to a
 fatal error, the script has stoped entirely, its not possible to continue
 from there

 One possibility is to treat this similar to the Database Error messages.

 The front end recieves the ugly message, Admin recieves a pretty message
 with some descriptive text as to why its as it is, and if an error has
 occured, they can click through to disable maintanence mode.. In doing so
 however, would in 90% of cases require the FTP credentials again to
 disable the mode (Which, asking for it again, is probably appropriate
 still)

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/13988#comment:4>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software