permissions

kishman155 · **Posted:** Mon Jun 27, 2005 6:56 pm

I am working for now a long time with cmsms and there is a question.

I haven´t got the time to test 10bethaX but is there a reason why there aren´t permissions to deny users
to change caching or make pages they are alowed to change not shown in menu?

mfg
Kris

Ted · **Posted:** Mon Jun 27, 2005 7:00 pm

I'm not totally sure what you mean. If they have access to edit the page, they can change anything on that page (including caching). Not sure what you mean about the make pages part of that question...

kishman155 · **Posted:** Mon Jun 27, 2005 7:12 pm

Sometimes its easier to gave user the permission to change content but not to change the caching or to hide a page in the menu or only to change the position in the menu.

i don´t trust users.

kris

Patricia · **Posted:** Wed Jun 29, 2005 3:35 pm

I agree with Kishman... as now the add/edit page has 2 tabs, it would be nice to have 2 different permissions (1 for each tab).
then, they could be able to edit a page, but not what we find on 2nd tab(options): headertags, active, cache, menu, owner, additional editors.
And why not, also different permissions if more than 1 block?
but I guess this is difficult...

in the same idea, in News module, it would be great to have 3 permissions:
1. add/edit/delete news (and as the content pages, they could modify only their own or being additional editor)
2. add/edit/delete categories
3. manage templates (summary and detail)

Ted · **Posted:** Wed Jun 29, 2005 3:48 pm

Well, different permissions for News would be easy. However, adding multiple permissions to pages increases the difficulty. There are several dynamic factors invovled with content types. For one, all content types don't have the same number of tabs. Only "content" has 2. But, you have now have the additional editors stuff. How do you assign users to one permission and not the other without it becoming a completely different interface?

I agree that permissions should be more fine grained and it should be system wide. However, I think it needs to be done from the ground up and should be a version 2.0 thing.

Thoughts?

kishman155 · **Posted:** Fri Jul 01, 2005 6:15 pm

There are many dynamic stuff in permission.

I think 3 permission are not enough.

I think we could use leveling to make permissions easier.

leveling
a nother database field called "level" at group_perms
There we could store the acces level
Level1=1
Level2=3
Level3=5
Level4=7
Level5=11
.
then we need a function to check how many levels this moduls need
like this;

Code:

function getlevel()
{
$level=array(
"write"=>1,
"read"=>2,
.....)
return  $level;
}

This function is needed to say the groupmanagment how many radio button
he should create and what is what for like news or somthing,

the administrator don`t need to check a permission anymore he will
check the radiobuttons to set what vor level the group have.

Then he call the permissions as usaly done from module but with one
field more where he checks the level.

if he hase permission he gets acces if not he gets '';

kris

permissions

Who is online