I'm using CMSMS 1.6.5 upgraded from 1.6.4.
I've gone through my pages adding my SiteOwner (group) as 'Additional Editor' to all the second level product description pages.
These pages are child pages of a top level page called 'Products'.
The SiteOwner group has permissions to:
Add Pages
Approve News For Frontend Display
Delete News Articles
Modify Any Page
Modify Files
Modify News
Remove Pages
Advanced usage of the the File Manager module
The SiteOwner group does not have permission to:
Manage All Content
With this setup I thought my client (SiteOwner) would be able to edit top level pages, not delete them. But they can delete all pages.
To stop someone deleting top level pages I have to remove the 'Modify Any Page' permission and then only the pages that they are 'Additional Editors' for will show up.
Is this correct?
Or can I configure it to allow editing of all pages, but deleting of only second level pages that they are 'Additional Editors' to.
Confused
Simon66
CMSMS 1.6.* Remove Pages permission confusion
CMSMS 1.6.* Remove Pages permission confusion
Last edited by Simon66 on Tue Sep 15, 2009 2:14 am, edited 1 time in total.
A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.
This must be Thursday. I never could get the hang of Thursdays.
Douglas Adams - The only sane person in the asylum.
This must be Thursday. I never could get the hang of Thursdays.
Douglas Adams - The only sane person in the asylum.
Re: CMSMS 1.6.* Remove Pages permission confusion
Simon66,
Modify-any-page, already gives them content-change permission to all-pages. The Manage-all-content, additionally gives them permissions to the options-tab (with show-in-menu, active, alias, etc...). So AFAIK did your users already have access to all the pages, with the permissions you gave "Modify any page", and with the additional "Remove pages", could remove them as well...
All pages were showing to the user already in listcontent, werent they? If they only were allowed to modify the second=level pages of a certain root-page, then you should take the modify-any-page away, then they only will have access to the pages they are specifically set to own/add-editor. The pages that show in the listcontent, will than be the pages that are accessible (and its parents for showing the hierarchy, but without permission, they arent accessible).
Ronny
Modify-any-page, already gives them content-change permission to all-pages. The Manage-all-content, additionally gives them permissions to the options-tab (with show-in-menu, active, alias, etc...). So AFAIK did your users already have access to all the pages, with the permissions you gave "Modify any page", and with the additional "Remove pages", could remove them as well...
All pages were showing to the user already in listcontent, werent they? If they only were allowed to modify the second=level pages of a certain root-page, then you should take the modify-any-page away, then they only will have access to the pages they are specifically set to own/add-editor. The pages that show in the listcontent, will than be the pages that are accessible (and its parents for showing the hierarchy, but without permission, they arent accessible).
Ronny
Re: CMSMS 1.6.* Remove Pages permission confusion
Thanks Ronny,
Yes I wanted them to have Modify-Any-Page, but only delete second level pages.
Or looking at it from a different perspective - locking in first level pages, but leaving them editable.
I read this in the 1.6 announcment:
– The “Add Pages” permission states that the user can create pages as children of pages that he is already an owner/additional editor of.
– The “Remove Pages” permission states that the user can only remove pages that he is an additional editor/owner of.
But I think it is all dependant on not having Modify-Any-Page.
Thanks for the reply
Simon66
Yes I wanted them to have Modify-Any-Page, but only delete second level pages.
Or looking at it from a different perspective - locking in first level pages, but leaving them editable.
I read this in the 1.6 announcment:
– The “Add Pages” permission states that the user can create pages as children of pages that he is already an owner/additional editor of.
– The “Remove Pages” permission states that the user can only remove pages that he is an additional editor/owner of.
But I think it is all dependant on not having Modify-Any-Page.
Thanks for the reply
Simon66
A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.
This must be Thursday. I never could get the hang of Thursdays.
Douglas Adams - The only sane person in the asylum.
This must be Thursday. I never could get the hang of Thursdays.
Douglas Adams - The only sane person in the asylum.
