[EMAIL PROTECTED] wrote:
> I've noticed a weird sitegroups behaviour and wonder if anybody else has
> noticed it:
>
> All the pages and styles belong to the administrator's sitegroup and only
> the content (that is articles and topics) belonging to the individual
> sitegroups.
> This approach worked fine so far but behaved unexpectedly on our
> development system: It was impossible to retrieve certain articles, topics
> and images from the database. After a reasonable debugging session the
> problem was identified: It seems to be ok to have all templates and styles
> belonging to the administrators sitegroup ? the entries in the host table
> however need to point to the proper sitegroups.
>
> Is this true?
It depends. Let me explain about sitegroups before relating it to your
environment. I'm assuming the visitor is logged in as a non-root user,
or is a anonymous visitor.
When you are logging into a host, you are also selecting what sitegroup
you'll be in. If you don't specify the sitegroup using a modifier, the
sitegroup field of the host record is taken as a default. For an SG0
site, the visitor will be required to specify the desired sitegroup,
since he can't stay in SG0.
Once the (non-SG0) sitegroup is selected, any object from that sitegroup
and SG0 is available for read access. Write access to SG0 is denied,
write access to objects in the sitegroup is governed by the regular
ownership system.
So when you say 'have the templates and styles in the administrators'
sitegroup' you mean SG0, yes, that does work. Any other sitegroup, no,
you can't share that across sitegroups.
If the articles and topics are in a sitegroup X, in order for a page to
be able to access them the visitor will also need to be in sitegroup X.
For non-SG0 hosts, this means that the host record sitegroup (to be used
as the default) will have to be X too.
> The weirdest thing is that I have a site fully working without the
> sitegroups ammended in the host table
I don't quite understand the above. Can you rephrase?
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
