[wp-trac] [WordPress Trac] #30261: Split all existing shared taxonomy terms on WP upgrade

[WordPress Trac]

#30261: Split all existing shared taxonomy terms on WP upgrade
-------------------------------------+---------------------------
 Reporter:  boonebgorges             |       Owner:  boonebgorges
     Type:  enhancement              |      Status:  reopened
 Priority:  high                     |   Milestone:  4.3
Component:  Taxonomy                 |     Version:
 Severity:  blocker                  |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------------

Comment (by Chouby):

 Replying to [comment:65 boonebgorges]:
 >It's a race that occurs when the database upgrade is run at the same time
 that a wp-cron is in progress. Something like this:
 > 1. wp-cron.php is hit, and wp_version_check is fired. (wp_version_check
 was the culprit in Chouby's case, but it could happen with any event, and
 it'll be liklier with events that require external requests and so take a
 second or two to complete)
 > 2. While the cron job is running, the db upgrade is fired in a separate
 process.
 > 3. The db upgrade schedules 'wp_split_shared_term_batch' and saves the
 cron array.
 > 4. The cron job finishes, and performs cleanup on the `$crons` array
 (rescheduling events, etc). This overwrites the cron array from step 3
 with the previous value of `$crons` (with events re- and unscheduled as
 appropriate).
 Just for information, there is already a ticket for this wp-cron bug:
 #13158

--
Ticket URL: <https://core.trac.wordpress.org/ticket/30261#comment:75>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform