[wp-trac] [WordPress Trac] #35146: Warnings are generated for a custom taxonomy named "terms"

[WordPress Trac]

#35146: Warnings are generated for a custom taxonomy named "terms"
--------------------------+----------------------
 Reporter:  willshouse    |       Owner:
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:  needs-codex   |     Focuses:
--------------------------+----------------------
Changes (by DrewAPicture):

 * status:  new => closed
 * version:  4.4 =>
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Replying to [comment:2 willshouse]:
 > I suggest treating this as a bug instead of just taking the "easy route"
 and saying it's "off limits"
 >
 > - Yes, it's blog software, but people also use it as a platform for many
 other things - partially because it is so flexible
 > - "Terms" seems like an fittingly abstract taxonomy name that could work
 well in many use cases
 > - It would be a small change to the core code to allow this flexibility
 >
 > That being said, do what you like. I'm not holding my breath for a fix.

 Respectfully, there isn't really a "fix" for this issue. Core has two
 established hooks for `get_` + your unprefixed taxonomy slug. "terms" is a
 commonly used keyword in WordPress vernacular. The recommendation would be
 to follow best-practice and prefix your taxonomy slug to avoid conflicts
 with core, other plugins or other themes. Perhaps `class-term` or
 something.

 Feel free to continue the discussion here if you'd like; a ticket doesn't
 need to remain open for discussion to continue.

 Related #31154

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