On 06.04.2006, at 10:45, Ralf Hirning wrote:
Jason,
this has nothing to do with the repositories.
1. Give each site a separate tree (/site1, /site2, ...) using the
Redirect
template for these root nodes
2. Create templates for each site to define the look-and-feel
3. Give the authors the rights to access their respective site only .
Problem: You cannot restrict templates to be used on certain paths.
So you must
think of a solution if this is important
Hi Ralf,
its actually straightforward to restrict access to templates using ACLs
For instance, group your templates per site and deny access to the
folders that a role should not have access to.
e.g. deny access to CONFIG: /modules/templating/Templates/samples and
the role will not see the sample templates.
Of course this might get tricky if you need read access to the
templates, but as long as you have different sites with a set of
allowed templates per site it should work fine.
Cheers
Boris
---------------------------
Magnolia Content Management
http://www.magnolia.info/
---------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
