Keep in mind that Magnolia's purpose is a web editing and publishing. Not active subscriber is rather special case, most likely a developer setup. Also the command can't be just turned on/off based on the subscriber configuration. It is more an arbitrary decision to delete (and deactivate) content immediately or go with the new staged deletion.
Sure, the developer case is a really special case, I'll probably write myself a simple task to switch the deletion behaviour depending on magnolia.develop=true property.
Transactional activation means that the activation (or deactivation) have to succeed on all subscribed public instances, or it will not be pushed to none of them.
Yes, but the question is about what should happen when the operation succeeded on all public instances but for some reason fails at the end in the authoring machine (which was more or less the result of my stupid try)? Does the push have to be rollbacked from every public machine? Or it is simply too late at this point? I'm just curious to know some of the inner workings but too lazy to read the code... :-)
Regards, Danilo. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
