WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am developing a site which uses custom taxonomies writer and artiste. I am using a custom taxonomy for writer because the site is a collection of old articles that I want to be searchable by author, and WordPress requires separate logins for each author, and only one person will be maintaining the site. Using my own custom taxonomy seemed the simplest thing to do. So I edited the theme and made a custom taxonomy for writer that allows the admin to specify writer and it shows up in the correct place. Some of the articles are about artists, and I want to search by artist as well, and so we have the artiste taxonomy (never mind the 'e').

Now, some artists are writers as well. So I want http://root/writer/artist-name to give me all articles which mention "Artist Name" as a writer, and http://root/artiste/artist-name which mention him as an artist. But WordPress says two tags in two different taxonomies cannot have the same permalinks, and tags the later one http://root/artiste/artist-name-2 (depending on which one was tagged later). I had imagined that (from a database perspective) each tag in a custom taxonomy would be stored depending on the taxonomy itself (like a weak entity, with a foreign key for parent taxonomy), so such collisions (as a design decision) do not make sense to me.

In the next step of development, I am going to make it so a specific writer or artiste query returns only that, but there be another superset query such as http://root/person/artist-name which returns both (i.e. all articles in which "Artist Name" is tagged as either writer or artist or anything else). Since the -2 is assigned to the later tag, and there is no clear way to predict if writer or artiste will be tagged first, this is problematic and inefficient for me.

So my question is, how can I change WordPress codebase (or database permissions) which will allow two separate custom taxonomies to have the same tag?

share|improve this question

closed as too localized by toscho Dec 18 '12 at 23:53

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

the issue is that slug is a unique key in the terms table. see this trac ticket. – Milo Sep 20 '11 at 19:50