• I am trying to use categories, tags and some more taxonomies to organize the content on different ways and I’m confronted with something that doesn’t make much sense:

    The slug has to be unique global to every taxonomy, meaning that one taxonomy term can’t have a matching slug with another taxonomy term..

    That means that you can’t have a category named ‘Vegetables’ if there is a tag ‘vegetables’. More than this: you can’t have the same category name -meaning slug and pathname- even if they have a different parent:

    ‘cat A’>’sub 1′
    ‘cat B’>’sub 1′

    From the pathname perspective (when using permalinks), /catA/sub1 is different from /catB/sub1.

    Is this considered an issue? Which is the logic behind it? How can be overriden to have this possibility of “same term name (and slug) + different taxonomy”?

Viewing 5 replies - 1 through 5 (of 5 total)
  • It is considered an issue by some… it’s a very well known issue, and presumably there’s some discussion going on as to how to address this, or whether it’s to be addressed at all.

    Personally, I don’t have a huge problem with it. Slugs are largely for internal use only. Unelss you’re particularly anal about your path names, then it’s not a problem.

    What it *does* allow though, is a very easy way to deal with the taxonomy without caring too much whether you’re working with tags or categories, and what levels of nesting they have attached to them.

    You can shuffle categories around right now. What happens when tomorrow you want to shuffle them under the same parent?

    You’re gonna see a message like:

    Sorry, you can't do that because you're anal about your path names.

    “So, Ivo, how DO you feel about threads like this?”

    I’m glad you asked.

    This has been discussed maybe 10,000 times since wp 2.3… without a solution, it doesn’t really belong in the ‘advanced’ forum.

    Thread Starter tomgf

    (@tomgf)

    I don’t have the intention of starting a discussion round # 10,001, but if this was discussed 10,000 times, how can it be that there isn’t a solution?

    Nevertheless, I think in this case the taxonomy system is not fulfilling some basic needs. At least in my case.

    I do care about the path names because I think that if there’s a logic behind the structure of the content this can – and maybe should – be reflected on breadcrumbs, path names, titles, etc.

    Last – but not least – if this question doesn’t belong to the advanced forum, where does it belong then…? Is this a ‘Miscellaneous’ issue…?

    since there’s about to be another major release in august which doesn’t address this, I think it’s safe to say that it’s not considered a high-ranking problem by the dev team.

    if you actually want a solution to this, then it’s better off in plugins & hacks I would say, as it is definitely going to require hacking.

    Paths is all this affects, by the way – breadcrumbs don’t use slugs as the link text, and neither do titles, so lets at least be realistic about how this affects things.

    you want cat/cars/honda and cat/bikes/honda, as opposed to having to deal with cat/cars/honda-cars and cat//bikes/honda-bikes… that’s *all* this affects.

    A little annoying? maybe… Serious? not really.

    Most issues like this can be resolved by throwing your bikes in cat/bikes and your cars in cat/cars, and then tagging them both ‘honda’ so you can find all your honda gear in /tag/honda

    if you wanted only honda bikes, you could tag your posts accordingly, and do /tag/honda+bikes, voila.

    Thread Starter tomgf

    (@tomgf)

    Thanks for your comments. I have a clearer picture and know better where to look for a solution. Or – considering your arguments – rethink about content organization.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Taxonomy: same slug, different taxonomy’ is closed to new replies.