I think by default everything gets created as the sitegroup of the user logged in - eg.an SG0 admin logged in as full admin, uploading blobs to a SG2 website will result in the blob ending up as SG0, most of the admin interfaces try to work around this by doing a setsitegroup($parent->sitegroup) imediatly after an update/create.
regards alan Francois Dumais wrote: >I was wandering what are the diverse consequences of working in a new site >group depending on the type of user you have chosen to login with? > >Another way of asking the question could be: does anything created in a new >site group inherit of anything particular (maybe security features, maybe >privileges, maybe accessibility, maybe visibility, etc...) when logged under >a given user (SG0 root, admin, user - OR - newsitegroup root, admin, user) >as opposed to being logged as another user be it admin, root, user of SG0 or >any other sitegroup (if this is possible but I think not ... but not >important here)? > >To be concrete. If I log as admin-password and start working on my new >sitegroup all the times, will there be properties inherent to that fact that >will affect something later on?? What are those things that can be affected >(if this is indeed the case)? > > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
