Robin Jackson wrote:
><note_of_thanks>
><to>Emile</to>
><msg>
>Thanks for the reminder to update admingroup in the SG after creating the
>group. Somewhere in the back of my mind I knew that at one point......but
>it obviously got lost in a core dump. ;)
></msg>
></note_of_thanks>
>
>The question I have for the group is more along the lines of nadmin
>functionality. When I log in as a member of the admin group for a site, I
>do not see my root web pages under the website tab. Rather, I see...
>
>Website must be created by System Administrator
>
You should be able to select Roots/Websites to toogle between hosts &
root pages.
if there are no hosts assigned to that sitegroup - that message should
appear on the Websites view.
Roots should show all root pages in that sitegroup..(if not, that sounds
like a bug..) - have a look at
Snippet: / hklc_adminsite_host / menu / 3,websites,Websites / by_root
>
>I also do not see the Style that is created for this site (which is a child
>of a SG0 Style as discussed previously).
>
I would guess that this is expected behaviour..
- the style list, lists all styles which are up=0 and sitegroup=Current..
since a child style would have up='a number', and that parent would have
sitegroup=0, it would not be displayed..
The problems with that where that the interface would have to understand
a bit better what was read only (eg SG0).. if it allowed you to browse
those trees....
It should be possible to modify the code
Snippet: / hklc_adminsite_host / menu / 4,styles,Styles / styles
to show 'shared styles', -> then allow you to edit a style if the
sitegroup was the same as the logged in user.
>
>When I log into the OLD admin site (with SG's enabled) I see....
>
>You're currently logged in with user Robin Jackson.
>Your current privileges level in sitegroup mt-xml is administrator.
>
>I do SEE my style though and can modify it.
>
>It does us no good to be able use nadmin and site groups if the
>Administrator can't see his styles and his web sites.
>
>I'll repeat....copying the entire style into another SG is not a valid
>option. While we want the user to be able to override element definitions,
>we only want them to be able to do that in an inherited mechanism. If we
>change core elements....we do not want to distribute changes to 6,000 users.
>Neither do we want 6,000 copies of our styles in the database....where
>essentially ASP users can see them.
>
I would suggest modifing the two files above to suit those needs... -
ideally this would be a configuration option -
$set[viewsg_objects] = "YES|NO";
'Show all SG0 data when logged in as Sitegroup user'
>----------------------
>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]
