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

WordPress Trac noreply at wordpress.org
Tue Oct 22 03:18:46 UTC 2013


#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):

 [attachment:25660.diff] attempts to cover the Low priority angle of this,
 by hooking into the cron lock transient's actions and re-scheduling the
 update checks to happen in 30 minutes (and +12-ish hours for the next
 normally scheduled check).

 It's completely untested, but attempts to block it delaying twice (over a
 greater than 5 minute period of time, to cover cases where cron is
 triggered is triggered multiple times within a few seconds/minutes). It
 seems like we can probably do that without too much crazy code, and cron
 modifications and is a easy win that's silent to the user.

 Adding a pre-update notification could be nice, however, we'd need to keep
 in mind that it may be 5 minutes before the twicedaily cron that we
 realise that we're going to apply a autoupdate (but, it could also be
 11hrs, 55minutes before hand that we know).

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


More information about the wp-trac mailing list