Page Type => Area Permissions not trickling down to pages
Permalink
I'm fairly new to Concrete 5 and have been looking around the forums where I see this mentioned a lot, but haven't come across a clear answer so far - I apologize if I've missed it.
I have several page types set up and have been editing their defaults via the Dashboard. I'm finding that often when I change the permissions for an area (specifically, what group can add which block types), my changes don't trickle down to pages of that type, even though their permissions are set to follow the page type defaults, and sub-pages are also configured to inherit the page type default permissions.
Wondering if anyone knows why this happens or how to fix it.
Thanks in advance for any pointers,
Maggie
I have several page types set up and have been editing their defaults via the Dashboard. I'm finding that often when I change the permissions for an area (specifically, what group can add which block types), my changes don't trickle down to pages of that type, even though their permissions are set to follow the page type defaults, and sub-pages are also configured to inherit the page type default permissions.
Wondering if anyone knows why this happens or how to fix it.
Thanks in advance for any pointers,
Maggie
New perms added to defaults will not affect already created pages unless you choose "setup on child pages" which will then launch a little menu pop up allowing you to choose which already created pages the new default permisions apply to.
Furthermore page type defaults only affect pages with that page type not every child page beneath it. So if you set defaults for the full page type they will not affect a right sidebar page type no matter where it is in the sitemap, hence the label page TYPE default.
C5 is ready for prime time perhaps its some other part of the equation that isn't and usually the community is there to help, however everyone here is volunteering their time to help others and sometimes stuff is left unanswered.
You also dont need luck you just need to use the search bar.
Furthermore page type defaults only affect pages with that page type not every child page beneath it. So if you set defaults for the full page type they will not affect a right sidebar page type no matter where it is in the sitemap, hence the label page TYPE default.
C5 is ready for prime time perhaps its some other part of the equation that isn't and usually the community is there to help, however everyone here is volunteering their time to help others and sometimes stuff is left unanswered.
You also dont need luck you just need to use the search bar.
Sorry, but it's not a good answer. The original question was about AREA PERMISSIONS of a page type and not a certain block permission of page type defaults. You cannot click on "setup on child pages" link at an area dropdown menu.
Has anyone figured out exactly how this works? When I generate new pages they don't seem to inherit the area permissions from the page default.
Permissions have always been tricky, but have been re-written since this question was asked.
To do this in newer versions of Concrete5 (I think 5.5+) you would first need to have advanced permissions turned on.
First set up your permissions for the actual page, set "Assign Permissions" to "Manually" if you leave it as "By Area of Site (Hierarchy)" then Editing the permissions on an Area will give, "The following area permissions are inherited from the page's permissions." > Override Permissions
Select the "Add Block to Area" and add the groups/users you would like to allow to add content.
Withing the Add Block to Area, pop up select "Details", within "Who can add what?" For each of your groups/users choose the dropdown and change from "All Block Types" to "Custom" then put a tick next to each of the blocks you want to be allowed to add.
Once all the permissions are set up you need to have them applied to your page. Depending on you site structure will depend on the permissions.
If you are editing a page that is a direct descendant of a page type then, select permissions and choose "From Page Defaults" if you are editing a page below this tree(ie a news detail page) then choose Subpage Permissions "Inherit the permissions of this page" or "Inherit page type default permissions" if you would like to have them follow the page defaults but don't want to have to set this on each new page.
If you are using a previous version 5.4.x or less then you need to do a similar process but the titles are different. I'll skip this unless someone is still using 5.4.x?
To do this in newer versions of Concrete5 (I think 5.5+) you would first need to have advanced permissions turned on.
First set up your permissions for the actual page, set "Assign Permissions" to "Manually" if you leave it as "By Area of Site (Hierarchy)" then Editing the permissions on an Area will give, "The following area permissions are inherited from the page's permissions." > Override Permissions
Select the "Add Block to Area" and add the groups/users you would like to allow to add content.
Withing the Add Block to Area, pop up select "Details", within "Who can add what?" For each of your groups/users choose the dropdown and change from "All Block Types" to "Custom" then put a tick next to each of the blocks you want to be allowed to add.
Once all the permissions are set up you need to have them applied to your page. Depending on you site structure will depend on the permissions.
If you are editing a page that is a direct descendant of a page type then, select permissions and choose "From Page Defaults" if you are editing a page below this tree(ie a news detail page) then choose Subpage Permissions "Inherit the permissions of this page" or "Inherit page type default permissions" if you would like to have them follow the page defaults but don't want to have to set this on each new page.
If you are using a previous version 5.4.x or less then you need to do a similar process but the titles are different. I'll skip this unless someone is still using 5.4.x?
Thanks for that Sean, I think my problem now is that the permissions on the file manager aren't working correctly in the latest concrete5 5.6.1.1, so it was leading me down the wrong rabbit hole.
I created an enterprise class website with this cms. As the site has grown I have come to realise that C5 is not ready for prime time. I wish I had known its weaknesses before I built an entire site around it.
Oh! Don't you love the responsiveness of the community? You posted this a couple of weeks shy of a year ago and I am the first one to respond. I have had that issue too. Another thing I should have done my homework on.
Good Luck! You're going to need it... a LOT of it!