I’ve come up with something unexpected, and would like some clarification.

I’ve registered an event listener for property changes on nodes that are 
mix:versionable.  As expected, an event is fired whenever a node with property 
changes is saved.  However, the event frequently fires before the node is 
checked in, which means that trying to retrieve the node when the event is 
fired results in the “old” version of the node being retrieved.

Two questions:
Is my assumption that a node should be saved before being checked in correct?
Should the event fire if the check-in hasn’t occurred?

I suspect that the answers are both yes, but confirmation would be appreciated.

Thanks,

Jim Tully

Reply via email to