Opened 14 years ago
Closed 13 years ago
#17683 closed enhancement (fixed)
'Categories' vs. 'Post tags'
Reported by: | scribu | Owned by: | |
---|---|---|---|
Milestone: | 3.3 | Priority: | normal |
Severity: | normal | Version: | 3.2 |
Component: | Taxonomy | Keywords: | has-patch commit |
Focuses: | Cc: |
Description
For some reason, the default hierarchical taxonomy is labeled 'Categories', while the default non-hierarchical taxonomy is labeled 'Post Tags'.
I suggest we rename the later to just 'Tags'.
Alternatively, we could rename the former to 'Post Categories'.
Point is, they should have consistent names.
Attachments (1)
Change History (8)
#4
@
14 years ago
Also note that 'name' and 'singular_name' are the only labels that contain the 'Post ' prefix.
We don't use 'Search Post Tags', 'All Post Tags' etc., which makes this inconsistency even more apparent.
#5
@
13 years ago
- Keywords ux-feedback removed
- Milestone changed from Awaiting Review to 3.3
- Type changed from defect (bug) to enhancement
- Version set to 3.2
I'm fine with just making them "Tags," as it was nomenclature that had been around a long time. I think to differentiate from tags on media, etc? Anyway, fine with me to shorten to just Tags.
Note: See
TracTickets for help on using
tickets.
They've been this way forever. I imagine it was a ux decision originally.