So I have a configuration where i'm using the Draggable Views CCK handler. I have to use CCK handler because i want to Prepouplate the ParentID from the new node form.
This functionality it important so I cant use the Native Handler.
I found that Draggable View CCK Handler uses the node_save() function. This gives the node a new "changed" value. Therefore it would trigger the notification emails, as well as mark the node as recently updated.
D6 node_save() doesn't allow for bypassing the "created" value being set. The D7 function does.
Therefore the only work around is to create a new CCK handler that operates directly with the content_field_parentid table and set the new parentid without using the node_save method.
Attached is the CCKNoUpdate Handler. I have tested this and it seems to work.
Greg
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | draggableviews-736590.patch | 4.28 KB | discipolo |
| #3 | draggableviews-736590.patch | 4.31 KB | discipolo |
| #1 | 736590-1.patch | 1.04 KB | msielski |
| draggableviews_ccknoupdate.tar_.gz | 1.43 KB | tomhung |
Comments
Comment #1
msielskiThank you for working on a solution to this problem! I have had the same issue with DraggableViews and Open Atrium and your module seems like a reasonable solution to me.
My only issue is that it appears you're using an integer field for the DraggableViews parent CCK field and both an integer or a node reference are supported. If integer fields are used then the field name ends in _value as your module uses, but if a node reference field is used it ends in _nid. Fortunately this data is available in the field data and the query can dynamically use it.
I've attached a patch which so far seems to work for me.
Thank you again.
Comment #2
Shadlington commentedSubscribing
Comment #3
discipolo commentedhere it is as a patch
Comment #4
discipolo commentedsorry, wrong one
here it is with comment #1
Comment #5
istryker commentedThank you for the patch, however 6.x in now unsupport. Closing this issue.