In a use case where another module is calling hook_node_update it is possible for revision information not to be passed.
Should the presence of '$node->revision' be assumed?
In a situation where we are using entity reference module and updating node parents in a custom module via a call... the following errors were generated.
Should the 'context_node_node_update($node)' function on line 211 rightly assume that '$node->revision' will or should always be available?
If no then this patch might be incorporated into the module.
Attached: Comment #1 for Patch
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | screenshot 6-6-2012 12-43-08 PM.png | 110.38 KB | webdeli |
| #1 | dont_assume_revision_information_is_available_.patch | 490 bytes | webdeli |
| dont_assume_revision_information_is_available_.patch | 489 bytes | webdeli | |
| screenshot 6-6-2012 12-43-08 PM.png | 112.07 KB | webdeli |
Comments
Comment #1
webdeli commentedComment #1.0
webdeli commentedUpdated issue summary.
Comment #2
lelizondo commentedFixed, please test and report back since I didn't do any deep testing.
Comment #3.0
(not verified) commentedUpdated issue summary.