Prevent "Design & Custom Template"?
Permalink
Is there a permission (or some other way) that would allow me to lock-down access to the "Design & Custom Template" option for block editing?
I don't want to give regular content editors/managers the ability to change design or template options like background images, padding, etc, for a content block... reserving that for only one or two high admins.
I don't want to give regular content editors/managers the ability to change design or template options like background images, padding, etc, for a content block... reserving that for only one or two high admins.
You should be able to click on blocks individually and set permissions in edit mode. You may need to turn on advanced permissions.
Thanks enlil.
Right, but I was looking for a way to set more of a GLOBAL default... which I could then OVERRIDE individually. So I didn't have to go to each Block on the site, and so the permissions are automatically set on new Blocks when they're created.
Right, but I was looking for a way to set more of a GLOBAL default... which I could then OVERRIDE individually. So I didn't have to go to each Block on the site, and so the permissions are automatically set on new Blocks when they're created.
This would probably be best suited for page type defaults. Where you set the block permissions on the defaults page and the permissions will pass to every page of that type created.
I guess I'm not following.
I define AREAS in my templates... into which my Content Managers can place Blocks (or Layouts). I want them to be able to do that. Just, not access the "Design & Custom Template" settings for the Blocks they create.
How can I do that in page type defaults?
I define AREAS in my templates... into which my Content Managers can place Blocks (or Layouts). I want them to be able to do that. Just, not access the "Design & Custom Template" settings for the Blocks they create.
How can I do that in page type defaults?
http://legacy-documentation.concrete5.org/editors/dashboard/system-and-maintenance/permissions-and-access/advanced-permissions/area-block-and-file-permissions
Thanks. I had already read that page. Which actually lead to my question.
The doc describes setting the permissions at a Block level. Which we've already talked about. I want something global, as a default. No such permissions appear to be accessible in the Page Type default.
In the Page Type default, I get the categories
Permissions for This Page Type
and
Permissions for All Pages Created Of This Type
Closest I can get from there is defining who can Edit Content for the entire page. There are no Details tabs to drill down into Blocks or Block Permissions... unless I'm completely missing it.
The doc describes setting the permissions at a Block level. Which we've already talked about. I want something global, as a default. No such permissions appear to be accessible in the Page Type default.
In the Page Type default, I get the categories
Permissions for This Page Type
and
Permissions for All Pages Created Of This Type
Closest I can get from there is defining who can Edit Content for the entire page. There are no Details tabs to drill down into Blocks or Block Permissions... unless I'm completely missing it.
I believe you mean, can you hide the design & custom template options form the pop up option list when clicking on a block...
This was possible previously setting this config value to false:
In fact we have an add-on that utilises this -http://concrete5.org/marketplace/addons/white-label/...
However, it looks like in newer version there is an other test that looks for $canEditCustomTemplate which always seems to be true, so this option no longer gets removed.
It may just be that concrete5 need to set an other config value against this so it can be managed.
This was possible previously setting this config value to false:
concrete.design.enable_custom
In fact we have an add-on that utilises this -http://concrete5.org/marketplace/addons/white-label/...
However, it looks like in newer version there is an other test that looks for $canEditCustomTemplate which always seems to be true, so this option no longer gets removed.
It may just be that concrete5 need to set an other config value against this so it can be managed.
