allow identical taxonomy slugs in different taxonomies

[nerrad]

Expected usage: I create a category named "Planning for WordPress Upgrades" with the slug "planning" and save. With permalinks on the url would be something like, " http://www.mydomain.com/%categorytoken%/planning.

I create a tag named "planning" and save. With permalinks on the url would be something like " http://www.mydomain.com/%tagtoken%/planning".

However: When saving the tag it will inherit the title of the preexisting category instead of saving as the tag I created. There should be no inheritance between taxonomy's.

Also, when editing the name in either the category or the tags the name will be changed in both the tag taxonomy and the category taxonomy. It is not possible to have different names for different taxonomies with the same slug.

Looks like this can't be fixed because the current db schema slugs have a UNIQUE key in the _terms table. I can understand wanting to make sure that there are unique slugs per taxonomy but isn't it overkill to have unique slugs across all taxonomies?

I understand the necessity for unique slugs with posts but the current default permalink structure would allow for like slugs in different taxonomies.

I propose that the SLUG field in the _terms table not be UNIQUE and the suggested attached patch be applied to allow identical slugs in different taxonomies

patch to be applied after removing unique index key for the slugs field in the _terms table

Taxonomy was designed to keep terms canonical between categories. We can revisit that decision, but not for 2.5.

Between taxonomies, I should say.

Replying to ryan:

Taxonomy was designed to keep terms canonical between categories taxonomies. We can revisit that decision, but not for 2.5.

Understood - hope it gets revisited :)

Keep in mind when revisiting. This decision regarding taxonomies affects not only category and tag intersections but also any future taxonomies plugin authors create. To keep terms canonical between category and tags is one thing but to force that on all future taxonomies might not be the best route to take.

I suggest adding a new 'canonical' paramater to the $args variable that defaults to true and running the current code. Plugin authors can set it to "false" (when calling wp_insert_term to allow inserting a slug with the same name as another taxomony for their taxonomy.

Of course this still requires dropping the index for slugs in the wp_terms table.

adds BOOL canonical param to $args for wp_insert_term

Please keep it unique until there is a full featured object modell for anything taxonomic. This here and there hushing leads to nothing but even more chaos. The way it is done now is not that nice but the most failsafe for the time being.

nerrad, even your patches do not fully reflect multiple taxonomies. you just passed it as useless parameter that's all. those different taxonomies have to be reflected in the datastructure as well.

Related: #3799 + #3683 + #5034 + #6542

see #8167, #4603

see #5034 too

Closed #12911 as duplicate

Related: #19169

Related: #5809

This is the same issue as #5809, just with different terminology. Closing as dupe as #5809 has patches.