[wp-trac] [WordPress Trac] #14877: Ability to create exclusive custom taxonomies
WordPress Trac
wp-trac at lists.automattic.com
Tue Mar 1 05:52:51 UTC 2011
#14877: Ability to create exclusive custom taxonomies
-----------------------------+-----------------------------
Reporter: benbalter | Owner: nacin
Type: feature request | Status: reviewing
Priority: normal | Milestone: Future Release
Component: Taxonomy | Version:
Severity: minor | Resolution:
Keywords: |
-----------------------------+-----------------------------
Comment (by nacin):
#16708 marked as a duplicate.
Here's what I'm planning here. Basically, a taxonomy will be able to
choose from a series of meta boxes.
- checkboxes (currently used for hierarchical taxonomies)
- input box (currently used for non-hierarchical taxonomies)
- radio buttons, based on the current checkbox meta box (exclusive)
- radio buttons, based on the current post format meta box (exclusive)
- a dropdown (exclusive)
There are possibly others, especially hybrids (like the current non-
hierarchical taxonomy box, only with a dropdown, like the current Trac
keywords box). Also possibly one other that escapes me, but I think I got
the main ones covered. I'm not even covering sortable term orders here,
which is a whole other idea.
Exclusive taxonomies (where you can enforce only one term being selected)
will be enforced server-side. The post format stuff will be entirely
abstracted into one of these meta boxes as well as the save handler.
This will also allow us to adopt a flag to turn off the popular terms
support, particularly the functionality in #3130, making the existing
hierarchical taxonomy box far more flexible. There will also be a flag,
where appropriate, for the option to choose no term, in the case of
exclusive taxonomies (otherwise you couldn't de-select the choice). There
can also be a flag for the ability to add new terms (possibly based on
permissions), the tag cloud as appropriate, etc etc.
I think this is also a perfect time to finally create a basic WP_Meta_Box
class.
This (as well as the class) is something I'm willing to shepherd for 3.2.
Support it during the scope sessions if you like it.
The ideas here have been bounced around a bit among other members of the
core team (at Tybee), but I'd like to see where else this can go to grow a
new API.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/14877#comment:7>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list