[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:  assigned
 Priority:  normal                   |   Milestone:  4.3
Component:  Taxonomy                 |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+---------------------------

Comment (by boonebgorges):

 Replying to [comment:11 batmoo]:
 > Any thoughts/discussion on using the multisite-like upgrade routine
 instead (i.e. process terms in small batches) to avoid the potential
 timeout issue?

 To my knowledge, WP updates have never used a system like this, so it'd
 have to be built for scratch. There'd be a number of complications to
 consider. For example, the Multisite network upgrader would have to be
 aware of the multi-pageload per-site updates.

 In this case, it's highly likely that only a very small percentage of
 sites will have more than a handful of shared terms. And those that do
 probably have some protocol in place for running WP database updates (see,
 eg, the utf8mb4 update in 4.2). So it seems to me like it wouldn't be a
 good use of effort to build a multi-stage upgrader just for this specific
 issue.

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