When a node is created and connected with multiple terms, then the node and the terms are connected in table "term_node" in the database.
But when a node is later edited and one or more of the terms are disconnected from the node, those changes are not recorded in "node_terms" in the database, not even after submitting the changes. Which actually means that the change is not recorded, and the next time a user accesses the node, the node will still be connected with those terms that the user was editing the node to disconnect the node from.
So now one has to manually remove the 'node - term connection' in the database, or just live with the bug that terms cannot be disconnected from nodes, or vice versa, once they are mode.
Best
Lennart
Comments
Comment #1
(not verified) CreditAttribution: commentedThe problem is not so simple...
When the term of some node is changed more than once and than changed back to one of previously selected terms during later editation you will get following error message after sending form (because newly generated PRIMARY key is already in the term-node table):
Ladislav
Comment #2
(not verified) CreditAttribution: commentedThe problem is not so simple...
When the term of some node is changed more than once and than changed back to one of previously selected terms during later editation you will get following error message after sending form (because newly generated PRIMARY key is already in the term-node table):
Ladislav
Comment #3
(not verified) CreditAttribution: commentedThe problem is not so simple...
When the term of some node is changed more than once and than changed back to one of previously selected terms during later editation you will get following error message after sending form (because newly generated PRIMARY key is already in the term-node table):
Ladislav
Comment #4
(not verified) CreditAttribution: commentedThe problem is not so simple...
When the term of some node is changed more than once and than changed back to one of previously selected terms during later editation you will get following error message after sending form (because newly generated PRIMARY key is already in the term-node table):
Ladislav
Comment #5
(not verified) CreditAttribution: commentedThe problem is not so simple...
When the term of some node is changed more than once and than changed back to one of previously selected terms during later editation you will get following error message after sending form (because newly generated PRIMARY key is already in the term-node table):
Ladislav
Comment #6
mousse-man CreditAttribution: mousse-man commentedIsn't the solution to use some DB trigger to change that, So everytime you update a node, you also execute an UPDATE trigger on term_node automatically? This would save quite some PHP code and transfer the 'effort' to SQL.
And yes, MySQL 4 can do triggers, don't know about Version 3.23. And of course PostgreSQL and Oracle can do it as well.
Comment #7
mousse-man CreditAttribution: mousse-man commentedSomething like
should do the trick.
This way, we can run the function from PHP.
Comment #8
jvandyk CreditAttribution: jvandyk commentedI can't reproduce this. In fact, I can't even understand what's being said.
This seems to imply that there is a problem with terms being lost from term_node. Testing with HEAD shows there is no problem.
I don't know of a "node_terms" table.
Closing.