Hey everyone,

I'm running Drupal 6.14 with CCK 6.x-3.x-dev (2009-Dec-07) solely for the multigroup module.

I've created a content type with a multigroup field, combining two content taxonomy fields: Role, a select list & Person, an autocompleting text field.

When I create a new instance of this type, I get the following error:

* user warning: Duplicate entry '35-0' for key 1 query: INSERT INTO content_field_role (vid, nid, delta, field_role_value) VALUES (35, 35, 0, 68) in /var/www/qhist/sites/qldpastonline.library.uq.edu.au/modules/cck/content.module on line 1277.
* user warning: Duplicate entry '35-0' for key 1 query: INSERT INTO content_field_person (vid, nid, delta, field_person_value) VALUES (35, 35, 0, 150) in /var/www/qhist/sites/qldpastonline.library.uq.edu.au/modules/cck/content.module on line 1277.

This happens for both new and existing terms. The new instance is being created correctly; the fields & their values display properly on the node view, and both fields' values are findable via Solr. So it appears to be working, I'd just like to avoid this warning if possible.

I was initially using CCK2 and have only just upgraded to CCK3; could it be an issue with the existing data created by CCK2? I'm at a point where I can easily restart the site fresh, if that would help with this issue.

Any help would be greatly appreciated.

CommentFileSizeAuthor
#8 NumberOfValues.png9.32 KBpvanerk

Comments

markus_petrux’s picture

Status: Active » Postponed (maintainer needs more info)

The cause of this issue could be in the land of content_taxonomy module.

Similar issues reported in that queue:
http://drupal.org/project/issues/content_taxonomy?order=last_comment_tim...

To figure out what happens, this needs to be debugged.

PS: Content taxonomy works for us in multigroup with no issues.

wuwei23’s picture

Thanks for the quick response, markus, I'll ask around there was well.

Incidentally, which version of content taxonomy are you running with CCK3? I'm using 6.x-1.x-dev (2009-Sep-13).

Cheers.

markus_petrux’s picture

Same version here. I have also tested with Content Taxonomy widgets of type freetagging, buttons and selects in a multigroup, with required and non-required fields. One thing we never do with these kind of fields is set the option that save terms in {term_node} table. This gave us some problems in the past, and we do not really need it.

wuwei23’s picture

I get the same error with and without the save terms option selected. I think I'm going to fire up a new site with CCK3 from the beginning and see what happens.

Thanks again.

eliosh’s picture

subscribe

bearstar’s picture

I am having an issue with newly created content. Does the following mean anything to you guys?

* user warning: Duplicate entry '####' for key 'vid' query: INSERT INTO node (vid, type, language, title, uid, status, created, changed, comment, promote, moderate, sticky, tnid, translate) VALUES (4673, 'profile', '', 'James Alborough', 2030, 1, 1283547441, 1283547441, 0, 0, 0, 0, 0, 0) in [path]/includes/common.inc on line 3528.
* The post could not be saved.

When I look in node_revisions, it is showing the nid to be 0 for any newly content created using types built in CCK3

The node_counter has the following settings:

Field nid
Type int
Length 10
Collation
Attributes
Null not null
Default 0
Extra
Comments

Am I right in thinking that the node_counter is where the node_revisions table is getting its nid?

karens’s picture

Title: Duplicate entry warnings on content creation » Duplicate entry warnings on content creation using Content Taxonomy

Making it clear that this applies only when using Content Taxonomy fields.

pvanerk’s picture

StatusFileSize
new9.32 KB

Hi Karen,

It also happens for other fields than the Content Taxonomy fields. It happens for every CCK field which has have "Number of Values Values:" more than one (see screenshot). I am using the 6.x-3.0-alpha3 releace of CCK. I saw this thread http://drupal.org/node/1032796 (Duplicate entry ... for key 'PRIMARY' in field_data_*) which states more or less the same.

Can I fix it somehow?

Thanks.

pvanerk’s picture

Changing the weight for filefield_path to 1 and for content to -1 solves the issue for me.

And for me everything worked again.

maedi’s picture

Can confirm that changing the weight also worked for me.