[wp-trac] [WordPress Trac] #25660: If an administrator triggers cron, a background update could temporarily lock them out

[WordPress Trac]

#25660: If an administrator triggers cron, a background update could temporarily
lock them out
-------------------------------------+------------------
 Reporter:  nacin                    |       Owner:
     Type:  defect (bug)             |      Status:  new
 Priority:  high                     |   Milestone:  3.7
Component:  Upgrade/Install          |     Version:
 Severity:  major                    |  Resolution:
 Keywords:  has-patch needs-testing  |
-------------------------------------+------------------

Comment (by dd32):

 my thoughts:
 - We could be overstating this whole issue, both me and nacin hit it
 because we were testing, and the only requests to the site were us.
 - 503 is a pretty specific status that should cause a heartbeat failure no
 matter what IMHO, a server shouldn't be spewing those
 - We can add a specific header to maintenance mode and trigger based off
 that 503 isn't specific enough
 - I don't believe for 3.7 we ''need'' a pre-update nag
 - I don't believe for 3.7 we ''need'' a update-delaying handler such as in
 my patch [attachment:25660.diff​] - It was more as a self POC

 I think as long as heartbeat is taken care of, we can iterate with the
 rest in future releases, no need to add a bunch of fancy smart logic at
 the last minute.

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