In this case it would be nice to have a "Site" prefix for all roles that have rights on a single site: Site Content Administrator, etc.
I would like to see the following:
1 - give an authenticated user access to editing of a certain "personal" page. This will be his personal page and he can edit everything on this page.
2- give this user the option, to be set by the site admin to create pages under his personal page and have right to edit these of course
3- Server admin option to set that when signing up it will create automatically a personal page for authenticated users.
This feature would create a kind of "myspace"
Also it would help to create certain sections of the website to be edit only by certain people. Like i have created www.lovemycaribbean.info and I would like to have certain persons just be able to edit the information of one island. That person will be only responsible for editing that section (menu item).
It would be a nice that their would be a feature that when page are edited or added, it will email the site admin, so that the site admin would know what is going on.
I like the fact you are getting ready to revamp these settings, I recently had an issue where your proposed changes would have helped.
Where do you propose the current "Administration Menu > Site Settings" role goes? I am thinking the Site Administrator role.
To me the idea of a feature to allow granting a user a page or node of pages that they can edit seems interesting. We already have some personalization via MyPage but that is only for exposing internally published content to be arranged into custom pages by the user.
Now its already possible to grant a user this ability to edit a page or node of pages if you create a role for the user and create the first page which will be the root page of his node and set the edit permissions and create child page permissions to the role you created. Add the user to the role and bingo he can edit his own subtree of the site.
The problem is if you want to do this for a large number of users your going to have a large number of roles which is difficult to manage and really goes against the idea of using roles in the first place which is basically to group users into permission buckets.
So to implement this feature to support that kind of use case it would be better to add an EditUserGuid column to the mp_Pages table and maybe a bool for EditUserCanCreateChildPages.
Also we would probably need a way to configure which features are vailable to untrusted users or taking away some features from some users.
I'll keep this idea in mind though right now I have a lot of other priorities above this idea.
As for the original post of this thread, you may notice it was from February 2005 so this is not my current thoughts. I mean hey that was back in 1.1 .NET days ;-)
The current thinking is:
Server Administrator = Admin in site which has IsServerAdminSite =true in the db which is only the first site created.
Site Administrator - role exists
Content Administrator - role exists
Content Author - role exists but up to you to grant it permission to edit pages
Blog Author - not implemented or planned to have feature specific roles. You can make any roles you like already
Forum Moderator - back burner - maybe revisit someday when the forums gets some love
So currently you can create a role for each of the islands and add users to those roles that should be able to edit. In the page settings for the top level page for an island set the Roles That Can Edit and Roles That Can Create child pages to the corresponding role for the island.
Hope it helps,
Thanks. I will implement it that way.
Keep up the good work!