> > We now need to programmatically activate (e.g.) mgnl:user "322" – and because > we cannot be sure that mgnl:folder 32 and 3 are already active too, we need > to activate them first as well. How do I have to setup the rules for > activating the mgnl:folder and mgnl:user nodes so that I only activate folder > 3, then folder 32, then user 333 including his list of roles and groups?!
I guess you will not like the answer as it is "you don't". The rules will filter content only based on the types. As the children are of the same type you can either include them all or exclude them all. What you want is write custom activation command that checks the activation status of the parents (all the way up to root or up to the first activated/modified parent) and activates those that are not active yet and only then activates the content that was actually requested for activation. Please beware that doing so you might publish content that was not actually approved for publishing in one of the upper levels. > > Thanks for your help... the faster the better! > > -will > > P.S.: The reason fro the urgency: The "funny" behavior I am seeing now when > activating the user "322" with allowed item type "mgnl:contentNode" (for the > list of roles and groups) is that the mgnl:contentNode nodes of user 321 and > 333 (all users in folder 32) are erased on public!!! The only time I've seen behavior like that was when the content was auto-created using install tasks and had different uuids. If that happens, activating content in the same path but with different uuid means that old content is removed (including all its children). Please double check that parent content has same uuid on author and public. HTH, Jan ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
