[wp-trac] [WordPress Trac] #18609: term_id collisions possible with InnoDB tables and global_terms_enabled
WordPress Trac
noreply at wordpress.org
Fri Aug 5 03:48:46 UTC 2022
#18609: term_id collisions possible with InnoDB tables and global_terms_enabled
-------------------------------------------------+-------------------------
Reporter: andrew_l | Owner: (none)
Type: defect (bug) | Status: assigned
Priority: lowest | Milestone: Awaiting
| Review
Component: Taxonomy | Version: 3.2.1
Severity: major | Resolution:
Keywords: has-patch needs-testing needs- | Focuses: multisite
refresh |
-------------------------------------------------+-------------------------
Comment (by dd32):
Replying to [comment:11 desrosj]:
> does .com still use global terms?
I believe it still uses a form of Global Terms, although I don't believe
it's using the WordPress Global Terms code directly - it appears a custom
plugin is in use (and likely was before the code was in core I think).
I know it was disabled on a subset of sites around the time of term
splitting, but I don't believe WordPress.com ever removed it entirely.
Replying to [comment:5 nacin]:
> If WP.com still uses global terms, they may be the only ones.
9 years later, I bet that holds true; I'd be surprised if many sites
remain that use global terms intentionally.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/18609#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list