Hello at all,
short question: is there a way to create roles which are allowed to
edit pages but denied from activating these (using Magnolia 2.1)?
The only solution I could imagine is installing a third magnolia
("editor") instance that activates its pages to the "admin" instance,
which itself is publishing them to the "public" instance. But as I
have to duplicate the repositories and startup one more instance on
tomcat reboot this solution is too resource intensive for my little
vserver.
Thanks for any suggestions,
best regards
Vivian
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
