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.

Comments

johnv’s picture

Component: Code » Rules
Issue summary: View changes

Re-assigning to a proper Component. D6 is not maintained anymore, but a D7 patch is welcome.

johnv’s picture

Version: 6.x-1.5 » 7.x-2.x-dev

Moving all remaining D6 issues to D7.

johnv’s picture

Version: 7.x-2.x-dev » 6.x-1.5
Status: Needs review » Closed (won't fix)

Moving 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.