Make WordPress Core

Opened 4 years ago

Closed 3 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:


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)

17683.diff (965 bytes) - added by scribu 4 years ago.

Download all attachments as: .zip

Change History (8)

@scribu4 years ago

comment:1 @scribu4 years ago

  • Keywords has-patch added

comment:2 @nacin4 years ago

  • Keywords ux-feedback close added

They've been this way forever. I imagine it was a ux decision originally.

comment:3 @scribu4 years ago

  • Keywords close removed

It's never too late to fix a bug. ;)

comment:4 @scribu4 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.

comment:5 @jane3 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.

comment:6 @scribu3 years ago

  • Keywords commit added

comment:7 @ocean903 years ago

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.