Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Problem with access permissions

Go to End

2 Posts   1137 Views


Community Member, 67 Posts

2 December 2009 at 4:23am

I have set security up so that there are 2 groups: Administrators, with unlimited rights, and Maintainers, whose rights are more limited. I have some pages which are in effect holders for subpages where the real content is (the end user first selects the parent page then the child page from a nested menu). I want Maintainers to be able to edit the content of the subpages but NOT be able to edit the parent (holder) pages (which are in effect part of the design of the website).

So, I set "Who can edit this page?" for the parent to just the Administrators group, then for the children, I check both the Administrators and Maintainers boxes, saving as I go along. But evidently Silverstripe does not like what I'm doing because it doesn't save the permissions (although no error comes up). When I move away from the parent page and then come back to it, the 'Only these people (choose from list)' radio button is still set for 'Who can edit this page?', but with no groups - it has forgotten them. This is the same with 2.3.3 and 2.3.4.

Am I misunderstanding something about the security in Silverstripe? Is it not possible for subpages to have more liberal editing permissions than their parent page?


Community Member, 67 Posts

2 December 2009 at 4:56am

LATER... It seems the problem runs deeper than that. I'm finding that in the case of a parent page with child pages, these group permissions are simply not retained at all, neither for the parent nor the children. What makes it more puzzling is that this only applies to existing pages and subpages. If I create a new parent page and add children to it, there is no problem, the permissions are retained. But nothing I do with the existing ones allows me to retain the permissions (nothing I can do via the CMS interface anyway). On simple pages there's no problem.

Does this make any sense to anyone?