Emiliano <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED].
..
> > UPDATE sitegroups set admingroup=4;
> >
> > I can now login as the new user+envida, and I am told that I am logged
into
> > sitegroup envida at adminstrative level.
>
> This is exactly how it works at the moment. In fact, I think this
> description deserves a place in the manual while the admin site lacks SG
> functionality, although I would quantify which sitegroup you want to set
> the admingroup for. The above works if you have one sitegroup.
>
Yeah, I'm lazy too.
UPDATE sitegroups set admingroup=4 where id=1; or
UPDATE sitegroups set admingroup=4 where sitegroup="whatever";
would have been better
> > I can see all the other sites that
> > are configured, also the ones that are in SG0. Is this how it's supposed
to
> > be? I assumed other hosts would be hidden from view. I cannot change the
> > ohter sites.
>
> Whether this is how it's supposed to be is for you, the user, to decide.
> I'm open to suggestions. This is how it works currently, yes. All content
> in SG0 will be available to all sites, read-only. You are not supposed to
> see sites other than those in SG0 or your own sitegroup.
>
> I realize SiteGroups can be used to attain a level of confidentiality for
> non-root users. The SG0 resources can not be confidential in the current
> concept.
>
Ah, then that's okay with me. In a production environment I just have to
make sure that only the adminsite is in SG0.
I'll go now and do a recompile of midgard-php, to check if Alexanders latest
commit solves the php probs.
> Emile
Cheers,
Armand.
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
