This issue arose when using the autotaxonomy feature of aggregator2 and I have filed appropriately there. When a new term is created, there is no checking that the term doesn't already exist in the same vocabulary. It can be observed without aggregator2. Create a new term. Create another with the same term name. It is created without complaint. This can cause a great deal of confusion and headaches when importing terms from other sources.
I don't believe that the module should complain about the duplicate term. It should simply ignore the creation of a new term node and return the term that is already there (so it doesn't break things like aggregator2 - which populates its data with the returned term id).
Comments
Comment #1
alexmc commentedI have a different approach. I would suggest that we have a means of merging those duplicate taxonomy terms. I dont think that one can prevent the "duplicate" terms from being created in all circumstances.
Comment #2
alexmc commentedIn case it is of help to you I am about to create a perl script which merges duplicate taxonomy terms.
Comment #3
magico commentedI don't think this is a bug but a feature.
What identifies the uniqueness of a term is it ID and not it's name.
Comment #4
lilou commented