Closed (fixed)
Project:
Drupal core
Component:
node system
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
7 Sep 2005 at 19:49 UTC
Updated:
5 Oct 2005 at 20:40 UTC
Jump to comment: Most recent file
i have a custom content module. when i create a node of this type, the node.type
field is correctly initialized. but when i create a revision of that same node,
the node_revisions.type field remains empty.
since a user cannot modify the content type from the gui, i don't understand why
the 'type' field even exists in node_revisions, but because it does, i assume
it's meant to be the authoritative value of 'type'. so that's the field i grab
for my custom module, and when it's not kept up to date, stuff doesn't work.
i'm going to try to attach a patch, but last time i tried it crashed my browser
and i lost my post, so there may not be a patch file here.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | update_5.patch | 992 bytes | killes@www.drop.org |
| #1 | node.module_hlslaughter_200509071333_0.patch | 1.95 KB | harry slaughter |
| node.module_hlslaughter_200509071333.patch | 1.95 KB | harry slaughter |
Comments
Comment #1
harry slaughterattempting to attach patch.
patch also includes a fix for the notices node.module generates and doesn't need to. if anything comes of this post, i'll be more precise with my patch files in the future :)
Comment #2
killes@www.drop.org commentedIndeed, the update produces a type field in node_revisions which shouldn't be there.
Comment #3
dries commentedCommitted to HEAD. Thanks.
Comment #4
(not verified) commentedComment #5
(not verified) commented