When setting the permissions of a 'section' to 'By Page Type Defaults (in Dashboard)' and setting Area/Block permissions, they are not applied correctly.
To demonstrate this, I did the following:
1. Set 'Home' (right_sidebar) page permission to 'By Page Type Defaults (in Dashboard)'
2. Set Right Sidebar page Defaults permission manually like:
Guest: Read
Registered: Write
Administrators: Checked all permissions
3. Exit edit mode and save changes
Now, no matter what permissions you set for existing/new blocks added to Areas, you always:
1. Can add/delete/position/copy to scrapbook any block type in any area.
2. Cannot edit/set design/custom template of any block, even ones you added.
Trying to sort this out
Jan 21, 2010 at 11:26 AM
Ok. So I think I've been able to replicate this problem.
The problem is that you set a particular page type's defaults, including its areas. This sounds like it's working.
Then, on a given page, if you set that page up to inherit the permissions from its default (which you set in the first step) it's working.
Then, if you add a new page, which is set to inherit ITS permissions from the parent page - that's when you run into trouble. It looks like the new page is created, and it's page-level permissions are set correctly. But then when you get into the areas, the area permissions from the default page aren't honored. Instead it thinks the area permissions haven't been set at all, and it inherits them from the page level permissions, which are more permissive.
The problem is that you set a particular page type's defaults, including its areas. This sounds like it's working.
Then, on a given page, if you set that page up to inherit the permissions from its default (which you set in the first step) it's working.
Then, if you add a new page, which is set to inherit ITS permissions from the parent page - that's when you run into trouble. It looks like the new page is created, and it's page-level permissions are set correctly. But then when you get into the areas, the area permissions from the default page aren't honored. Instead it thinks the area permissions haven't been set at all, and it inherits them from the page level permissions, which are more permissive.
Would like to see this fixed
Jan 19, 2010 at 11:18 PM
Would like to see this fixed or find a work around.
Currently, if for example you want to disable the Auto-Nav (or any other) block so somebody doesnt begin to make a mess of things you have to do it all manually. You need to set the permissions for each and every block type on every block area for every individual page and page type. Its a mess.
If the add block permissions could be inherited automatically from the page type default then this would be of significant help. Or if there is another way of doing the same thing I would love to hear about it.
Currently, if for example you want to disable the Auto-Nav (or any other) block so somebody doesnt begin to make a mess of things you have to do it all manually. You need to set the permissions for each and every block type on every block area for every individual page and page type. Its a mess.
If the add block permissions could be inherited automatically from the page type default then this would be of significant help. Or if there is another way of doing the same thing I would love to hear about it.
Please look into it
Jan 28, 2010 at 1:44 AM
I've launched a new site, islam.gov.kw, and now having this issue. Clerks that are entering news can see all types of blocks and can add any of them. I really need to limit their access to a small set of blocks only (mostly content, image, flash and html).
defaulting areas to specific block types only
Mar 11, 2010 at 6:56 PM
Does anyone have a resolution for locking down an area in the page type (that would later be inherited by every created page automatically) to accessing only specific block types?
okhayat
Partially working on By Area Of Site
The problem is when a sub page permissions are inherited from that Page, Area/Block permissions are not inherited.