Currently the roles allow only read/write, read only and deny access.
There is no "activation" setting, but I assume (have not tried it yet!),
that you could deny access to the subscriber setting (e.g. create a role
and deny access to "/subscribers/SubscriberConfig/0004").
So you would have roles with read/write access to the dedicated node
tree and denial for the other node trees. You will also need to
configure a Subscriber for every node tree you want to publish. At last
you may want to try to create publishing roles, which have read access
to the dedicated subscriber and deny the other subscribers (I just
assume, but have not tried that yet).
Another thought: If you have a few websites with same or similar
template scripts, that should be better to have all in one instance.
However, if each website has different JSPs/Servlets, it may be easier
to have each of them in their own web app instance, since you may loose
the benefit of performance (one JSP for different websites). In that
case you may want to concentrate on easier maintenance and user setup.
hth
Paul Worrall wrote:
If I have everything in the same instance with each web site
redirected to a different content node can I have author instances
dedicated to publishing to one of those content nodes?
Or will an author instance have to have all the content nodes
representing the sites?
tia
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
