Dashboard > Community Wiki > ... > Administration > Setup editor role for a site
Setup editor role for a site Log In View a printable version of the current page.

Added by GrĂ©gory Joseph , last edited by Boris Kraft on Aug 21, 2008  (view change)
Labels: 

Setup Editor role for a site

If you want to run several sites on your magnolia instance you want to give them rights so that they can only see their own content:

Suppose you have a strucure like this

/site1
/site2
/site3

What is to be done:

1. Create an editor role with the necessary rights in the config repository.

Read only   | Selected and sub nodes | /modules/adminInterface/config/menu/website
Read only   | Selected and sub nodes | /modules/templating/templates

and grant access to / (and not sub pages) in the website acl. You can take the pre-installed editor role

Read only   | Selected and sub nodes | /$

For Magnolia versions < 3.1 add:

Read only   | Selected and sub nodes | /tmp/fckeditor

This is necessary if your users are going to upload images through the editor in order to workaround an ACL issue (see MAGNOLIA-1162).

2. Create roles for each site with the following right (example /site1):

Read/Write  | Selected and sub nodes | /site1

3. Give the editor both the rules of an editor and of the according site-role

The tricky part is the $ in the acl which works because the pattern matching uses regular expressions.

Ralf (ralf at hirning.de)

In its previous incarnation on JspWiki, this page was last edited on Feb 9, 2007 11:01:05 AM by Magnolia
Other known authors include :

  • RalfHirning
  • GregoryJoseph
Powered by a free Atlassian Confluence Open Source Project License granted to Magnolia International. Evaluate Confluence today.
Powered by Atlassian Confluence 2.7, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators