[wp-trac] [WordPress Trac] #30335: Splitting shared terms on term update breaks backward compatibility when using an old term_id

[WordPress Trac]

#30335: Splitting shared terms on term update breaks backward compatibility when
using an old term_id
--------------------------+--------------------
 Reporter:  boonebgorges  |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  high          |   Milestone:  4.1
Component:  Taxonomy      |     Version:  trunk
 Severity:  blocker       |  Resolution:
 Keywords:                |     Focuses:
--------------------------+--------------------

Comment (by boonebgorges):

 In [changeset:"30336"]:
 {{{
 #!CommitTicketReference repository="" revision="30336"
 Don't split shared terms on term update.

 Splitting shared terms means assigning a new term_id to a given
 term_taxonomy_id.
 It was uncovered that this change could cause problems for sites that have
 cached the original term_id somehow - say, in postmeta - since future
 lookups
 using that term_id will now fail.

 Removing for 4.1-beta1. We'll look at improvements to backward
 compatibility
 to try to get this back into a later beta.

 Props mboynes.
 See #30335.
 }}}

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