Hi,

There is a bug that appear when you put 2 content taxonomy field which are looking in 2 different vocabulary in one node.

There is my taxonomy

Recipe (vocab)
- By plate (parent term)
-- Entries
-- Dish
-- Serves
-- Amuse mouth

Universe (vocab)
- Curious cuisine
-- Perles
-- Spices
....

Then, I created content taxonomy in my content (see my screenshot).

The problem is that if I don't check at least 1 checkbox for each list in the "Univers" group of field, when I validate the form I have the following error :

user warning: Duplicate entry '1-3' for key 1 query: INSERT INTO dp_term_node (nid, tid) VALUES (3, 1) in D:\drupal\includes\database.mysqli.inc on line 151.

It's very strange, if I don't check one list on the "Catégories de recettes" group field, I don't have this error. This error only appear with "Universe" group field.

CommentFileSizeAuthor
#1 taxonomy_content_bug.png9.98 KBzmove

Comments

zmove’s picture

zmove commented
StatusFileSize
new taxonomy_content_bug.png9.98 KB

I forgot the screenshot. Say to me if you want more informations.

zmove’s picture

zmove commented

After some tests, the behavior of the module don't seems to be affected. If I check or uncheck some taxonomy terms, the node is well updated.

But the problem is that my node is available to public so I can't let this PHP error in it.

zmove’s picture

zmove commented

I'm on this bug since 4 days, I still don't have a solution. Anybody could help me and confirm if, in the same situation, still have the bug ?

zmove’s picture

zmove commented
Priority: Normal » Critical
AltaVida’s picture

AltaVida commented

I've noticed the same issue. The problem appears to be that the #default_value form element is getting set sometimes when it shouldn't.

As above, if the first taxonomy has a #default_value of 3 (tid=3), the #default_value for the second taxonomy form element will also be 3 when it should be undefined (there are no items selected).

Even though none of the available #options for the second vocabulary include the number 3, the form still gets rendered with 3 as it's default value. This is why applying any selection to the second taxonomy fixes the problem.

Temporary workaround:

Create a 'none' term in the second taxonomy and always select it when there are no terms to be used from this taxonomy.

PS. I'll see if I can create a patch, but I'm newbie when it comes to submitting patches here.

just-work’s picture

just-work commented

bumping in hopes that someone will work on this, I would be willing to fund a fix

llribas’s picture

llribas commented

more info on this bug:
http://drupal.org/node/223238

magnus’s picture

magnus commented
Status: Active » Closed (won't fix)

Cleanup of old issues. According to maintainer: "active development is only done for the 6.x branch! 5.x is not supported any more".
Reopen issue if problem still exist in 6.x branch.

plan9’s picture

plan9 commented

Any patch for this?