Dear Magnolians
We're experiencing all sort's of "funny" behavior when trying to activate
content programmatically. Consider this structure in the users repository for
example
- public (mgnl:folder)
- 1 (mgnl:folder)
- 2 (mgnl:folder)
- 3 (mgnl:folder)
- 31 (mgnl:folder)
- 32 (mgnl:folder)
- 321 (mgnl:user)
- 322 (mgnl:user)
- 333 (mgnl:user)
- ...
- 33 (mgnl:folder)
- ....
- 4 (mgnl:folder)
- 5 (mgnl:folder)
- ...
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?!
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!!!
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
