0

Whenever I invoke register_taxonomy in my site's custom plugin, all taxonomies are created as children of the blog post-type in WordPress by default. I just want them to be top-level items in WordPress, not children of the default blog post-type. I reviewed the register_taxonomy array parameters extensively and don't see a way to do this.

Using Admin Menu Editor, it's pretty simple to move custom taxonomies into their own admin menu. But at the system level, is their some hook to make a custom taxonomy its own entity inside of WordPress?

Using breadcrumbs as a mental model, this is the way things currently are:

  • Home > Blog > Custom Tax

I just want:

  • Home > Custom Tax
  • I've written a very extensive article about modifying the menu. In case you find your answer there, please add an answer below. – kaiser Jan 6 '16 at 17:32
  • I think there is some confusion between admin and permalinks. To remove the blog prefix from permalinks use the with_front argument (example). – fuxia Jan 6 '16 at 18:35
-1

No. As far as the admin menu is concerned the taxonomies are always "below" the content they apply to. You will always need to directly manipulate the menu structure to change this.

  • How would you recommend addressing the incorrect permalink and subsequent breadcrumb trail? – serraosays Jan 6 '16 at 17:24
  • Oddly the permalink does not include the parent post-type but the breadcrumb trail does...weirdly inconsistent implementation. – serraosays Jan 6 '16 at 17:27
  • Mark, this is not really an answer. A real answer would show how to achieve (a) removing a submenu item and (b) adding a top menu item. – kaiser Jan 6 '16 at 17:34
  • @kaiser, sorry but I am not in the habit of providing code for something that I think is a bad design when there is no evidence that there is an actual reasonable need for it. Taxonomies are meta of content there is no logical reason to divorce them from the content at the UX level. – Mark Kaplun Jan 6 '16 at 17:47
  • Please do not assume that you have covered every possibly available and valid use case. A standalone taxonomy is a very valid use case in lots of situations. Example: imagine handling global states for various states in your application. Why would you add the UI to every bit of the application over and over again? Again, please provide a full answer or convert it to a comment. Thanks. – kaiser Jan 6 '16 at 18:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.