Something about permissions (1.6.5)

[Sonya]

1. Group requires at least one permission:
-----------------------------------------------------------
Create a new group, assign any single permission to the group, try to remove the assigned permission from the group, so that there are no permissions at all. After submitting the checkbox is still selected, so that you are not able to delete the permission. If it works as desired, then a message would be nice, so that it does not look like a bug. Related topic http://forum.cmsmadesimple.org/index.ph ... 183.0.html


2. The permission is not used in CMS Made Simple
--------------------------------------------------------------------
Advanced usage of the the File Manager module (at least I could not find any reference to this permission in the source) Double "the" in permission name is original

[Sonya]

3. Additional editors are able to create 1st level pages:
----------------------------------------------------------------------
1. Create new Group with the the permission Add page.
2. Create new User and assign him into the group created above.
3. Add user as Additional Editor to a page placed in the 1st level.
4. Log in as this user. You are able to copy the page and thus create a new one in the 1st level.

Possible solutions:
1. There should not be the option Parent: none in the Copy Content Item screnn as the user is NOT allowed to add pages on this level.
2. There must be another permission: Copy Pages that can be granted separately from Add Pages permission.

[calguy1000]

You know that the proper place for this stuff is in the forge right?

because in about a week this forum topic will not be easy to find, and therefore it'll be forgotten.

[Sonya]

You know that the proper place for this stuff is in the forge right?

Will be done.   I am not sure everything listed above is actually a bug or just works as desired. Or probably I have misunderstood the permissions concept.

[calguy1000]

#1 is a known issue...  but not warranted important enough to fix in 1.6.6

#2 ... sounds like a bug

#3 ... sounds like a bug.

[RonnyK]

2# seems fine by me.... The code checks for...

function AdvancedAccessAllowed() {
return $this->CheckPermission('Use FileManager Advanced');
}

which explains as well why it shows at a lower level in the group-permissions listing...

Ronny

#3 will be tested....

[Sonya]

2# seems fine by me.... The code checks for...

OK, this is a kind of permission that does not allow anything in the core installation, but it can be used in other modules dealing with files. Right?

[RonnyK]

Sonya,

this permission is used in FileManager, which is a core-module... With this permission set AND the tick in FileManager to use advanced mode, you will get access to the full backend-folder listing in FM, instead of /uploads as top-level...

Ronny

[Sonya]

this permission is used in FileManager, which is a core-module... With this permission set AND the tick in FileManager to use advanced mode, you will get access to the full backend-folder listing in FM, instead of /uploads as top-level...

AND - was the most important part Now it is clear. Thank you!

[RonnyK]

Yep,

I only capitalized it, not coloured it

Ronny