By tinem on

I have used weeks to figure out why I get this error but haven't found a solution yet and hope some one can help, please?

When editor update a node get a lot of these errors for each node that get updates:

Message Duplicate entry '14-1179' for key 'PRIMARY' query: INSERT INTO term_node (nid, vid, tid) VALUES (383, 1179, 14) in /home/www/MY SITE/modules/taxonomy/taxonomy.module on line 724.

Don't see this error if I as admin update a node.

⋅ Categories: Drupal 6.x

Comments

VM’s picture

VM commented

have you looked at the rows in the taxonomy table to determine where the duplicate entry is?
Have you removed it from a test database to determine if the message clears?

tinem’s picture

tinem commented

Thanks VM for trying to help. I can't see any problems in table and don't understand your second suggestion, sorry.

I also get this sometimes location 2016-07-05 10:26 Conserving lid 374 due to uniqueness. and can see many other have this problem but can't figure out how to solve it, but maybe these two errors have something to do with each other?

VM’s picture

VM commented

the message indicates that there is a duplicate entry in the table. Export to excel and locate it. Once located remove the duplicate entry and test.

PMatwyuk’s picture

PMatwyuk commented

Hi Tine,

I don't know what site you are watching more so I'm going to include a response here as well.

VM makes a great suggestion for putting the table data into a spreadsheet to see if you can find the duplicate entry(ies) more easily. You can also use SQL to find duplicates (http://stackoverflow.com/questions/2594829/finding-duplicate-values-in-a...)

You mention that only those with the editor role are getting these errors. Would it be possible to see all the errors the page displays instead of just this one? Could we also know what version of D6 you are using? The permissions your admin role has and your editor role has? Finally any other taxonomy related modules you may be using and their versions?

I feel that additional information may be able to help debug this much faster.

You could also trying using the devel module or the masquerade module to switch to an account with an editor role to see what happens. Then to other roles and see if it only affects the editor role or everyone but the admin role.

Hope this helps and I look forward to hearing back.

Cheers,

Pete