Hi,
I've created a simple content type with a title, a taxonomy term and body field. Permission is set for authorized user to create new content, edit and delete own content, and clone any and own nodes. I've set the cloning method to "Save as a new node then edit." If I DON'T reset the publishing options to defaults (i.e. leave the box unchecked), the module works as expected. However, if I do reset the publishing options to defaults (i.e. check the box), I get a warning (see below). Interestingly, the node is created, but the taxonomy term and body field are not copied.
Here is the warning I'm getting: PDOException: SQLSTATE[HY000]: General error: 1366 Incorrect integer value: '' for column 'sticky' at row 1: INSERT INTO {taxonomy_index} (nid, tid, sticky, created) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3); Array ( [:db_insert_placeholder_0] => 19 [:db_insert_placeholder_1] => 25 [:db_insert_placeholder_2] => [:db_insert_placeholder_3] => 1313489942 ) in taxonomy_field_insert() (line 1673 of /home/.../modules/taxonomy/taxonomy.module).
Any advice you can offer is greatly appreciated.
JB
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | 1250670-8.patch | 1.19 KB | pwolanin |
Comments
Comment #1
anonym-developer commentedsub
Comment #2
moshe weitzman commentedbased on the second subscriber, I'm thinking that this is a legitimate bug so tagging.
Comment #3
robloachMind updating the module to -dev?
Comment #4
pwolanin commentedLooks duplicate to #1375988: Cloning fails when one of the fields is a Term Reference
Comment #5
jebeaudoin commentedThanks, Rob. Looks like there's a workaround at #1375988. Sorry I didn't see that when I first reported the issue.
JB
Comment #6
pwolanin commentedActually this issue is older and more details so I'll close the other as duplicate.
Comment #7
pwolanin commentedLooks like this might actually have been resolved by this core change #1050466: The taxonomy index should be maintained in a node hook, not a field hook, but the patch won't hurt.
Comment #8
pwolanin commentedRolling back to core 7.10 tag, I confirmed this patch should fix the issue until core 7.11 is out.
Comment #9
pwolanin commentedcommitted
Comment #10
pwolanin commented