1. If I add a term to a node that already has this term, the DB complains "Duplicate entry '8-21' for key 1 query: INSERT INTO term_node (nid, vid, tid) VALUES (21, 21, 8) in [...]/taxonomy.module on line 699."

2. If used with Drupal-dev, which warns about E_ALL violations, we get a PHP warning about "undefined index: 'term'" (on the '#default_value' => $context['terms'] line).

3. If the taxonomy module is not enabled, we get a PHP error about undefined function taxonomy_get_vocabularies.

Comments

mooffie’s picture

[...] get a PHP warning about "undefined index: 'term'"

(My typo: It should be "terms".)

infojunkie’s picture

Assigned: Unassigned » infojunkie

Thanks for your report I'll work on these issues.

infojunkie’s picture

Status: Active » Fixed

Fixed in both D5 and D6. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

ayesh’s picture

Component: Code » Core
Status: Closed (fixed) » Active

Unfortunately, I'm getting the same error when publishing (both published and unpublished nodes at once) node using VBO.

infojunkie’s picture

There are 3 errors reported in this issue. Which one(s) are you experiencing?

ayesh’s picture

First one.
I have created a View to display user's own nodes, both published and unpublished ones. If I select any node(s) -- buggy against both already unpublished and published nodes) -- and click on the "Publish" action, I get the exact same error (but line is different)described in #1 error.
user warning: Duplicate entry '15-26' for key 'PRIMARY' query: INSERT INTO term_node (nid, vid, tid) VALUES (26, 26, 15) in /path/to/drupal/modules/taxonomy/taxonomy.module on line 713.

I found some other bugs too, I'll open issues with more information as far as I can help. Thank you for developing this great module.

infojunkie’s picture

Are you using other taxonomy-related modules? For example: #361509: Duplicate entry for taxonomy SQL query

bojanz’s picture

Status: Active » Postponed (maintainer needs more info)
bojanz’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)

No other info provided by the user. Maintainer provided a possible explanation in in #8.

ayesh’s picture

Status: Closed (works as designed) » Closed (fixed)

Sorry if I'm mis-categorizing the issue status. But with the latest DEV version, problem seems to be solved.
And for #8's issue mentioned, it was not the problem I think.
Thanks for making VBO even more awesome.