WordPress.org

Make WordPress Core

Opened 12 years ago

Closed 7 years ago

Last modified 7 years ago

#11576 closed enhancement (maybelater)

The future of the 'uncategorized' category

Reported by: prettyboymp Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.9
Component: Taxonomy Keywords: needs-patch
Focuses: Cc:

Description

Is there any plan for removing the 'Uncategorized' category, or at least removing its requirement? Some users want the ability to only show the_category() when the post is part of a real category. Also, with the introduction of custom taxonomies in 2.9, not all hierarchical taxonomies will have a default term, so this flexibility needs to be introduced anyway.

I'm curious why the default category was introduced in the first place? Was it solely for permalink handling?

If attachment:ticket:10122:hierarchical_metaboxes-2.patch is accepted (specifically handling hierarchical taxonomies as int) the following just needs to be added above the checkbox list to allow deselecting of all terms from the taxonomy:

<input type="hidden" name="tax_input[<?php echo $taxonomy?>]" value="" /> 

Change History (11)

#1 @scribu
12 years ago

  • Milestone changed from Unassigned to 3.0

#2 @sirzooro
12 years ago

  • Cc sirzooro added

#3 @ryan
12 years ago

It was introduced for permalinks, IIRC. I would love to make it optional. Many themes are coded to assume there will be one, however.

#4 @scribu
12 years ago

It's not present in custom hierarchical taxonomies, which is good.

#5 @Denis-de-Bernardy
12 years ago

  • Keywords needs-patch added
  • Milestone changed from 3.0 to Future Release

#6 @filosofo
11 years ago

  • Owner filosofo deleted
  • Status changed from new to assigned

It makes sense but would involve a significant change in behavior for get_permalink()

#7 @kevinB
11 years ago

  • Cc kevinB added

#8 @mikeschinkel
11 years ago

  • Cc mikeschinkel@… added

#9 @solarissmoke
10 years ago

Related/duplicate: #14901

#10 @chriscct7
7 years ago

  • Resolution set to invalid
  • Status changed from assigned to closed

I'm going to say this will probably never, or at least not in the near future be up for removal (given its 5 years later and its still there). As this is more of a question, and there's nothing to implement, closing as invalid

#11 @helen
7 years ago

  • Milestone Future Release deleted
  • Resolution changed from invalid to maybelater
Note: See TracTickets for help on using tickets.