Closed (won't fix)
Project:
Workflow
Version:
6.x-1.5
Component:
Rules
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 May 2012 at 11:19 UTC
Updated:
10 Mar 2014 at 11:43 UTC
Jump to comment: Most recent
The problem arises when you have set up several events triggered by the same hook. In my case the event "Workflow state has changed" and "After saving new content" are invoked in hook_nodeapi($op = 'update'). Due to the default module weight the workflow event is fired first, modifies the saves the node. The second event has the condition "Node is new" which of course doesn't apply any more and leads to unexpected system behavior.
So let's keep the $node->is_new flag, so that subsequent rules can interpret the node state properly.
| Comment | File | Size | Author |
|---|---|---|---|
| workflow-rules-keep-is-new-flag-1.5-patched4.patch | 481 bytes | gnindl |
Comments
Comment #1
johnvRe-assigning to a proper Component. D6 is not maintained anymore, but a D7 patch is welcome.
Comment #2
johnvMoving all remaining D6 issues to D7.
Comment #3
johnvMoving back to D6, which is not maintained anymore.
D7 has had a major clean-up, and this problem should not apply anymore to the D7-version.