AnsweredAssumed Answered

Deleting node causes onDeleteNode to fire twice....

Question asked by marcus on Jan 12, 2007
Latest reply on Jan 12, 2007 by kevinr
If you delete a node that gets sent to the archive, the beforeDeleteNode and onDeleteNode policy gets fired twice, without any to determine which event was the removal of the node from its original parent. Is there another way I can bind to the event that gets fired only when a node is removed from a parent once? I've tried binding to associations before without any luck (I think there's a thread still floating around for that)…

Outcomes