Advanced Permissions

Permalink
Hi,

I wonder if there's anyone out there who's worked with advanced permissions in c5?

I'm developing a site that will be used by someone else and I need to restrict what they can do in respect of editing.

For instance, I need to lock the autonav block used for the main navigation so that the user can neither edit it or add further blocks of this type.

Any available help would be great.
Tony.

 
frz replied on at Permalink Reply
frz
you can easily do that.. be sure to turn advanced permissions on as quickly as you can in building out your site or you may end up with some funky permission settings after the switch (fixable, just funky)..

once you have a page setup viewable/editable etc to the right group, go click on the block area, or even a specific instance of a block and you should see permission settings for them as well.

im gonna be doing a screencast on this soon, but its reasonably intuitive if you just poke around the UI in advanced mode.
Fluvius replied on at Permalink Reply
Thanks for that information, it was useful but I still have a couple of questions that perhaps you could help me with.

I turned on advanced permissions by adding
define('PERMISSIONS_MODEL', 'advanced');

to the config/site.php file, but I am a bit confused about where I should now look to limit editing on blocks.

I have created a new user group called editors and then created a new user - who will be the end user - to this group, thinking I can attribute certain privileges to that group, but I'm a bit lost on how to do that, or in fact if it's really necessary at all...?

And where do I set the privileges to restrict editing on specific blocks in the template?
I clicked on the 'default' button next to the page type and set it into edit mode but when I clicked in the autonav block which I want to lock against editing and clicked to 'Set Permissions' there was a message at the top of the popup windows stating "Permissions for this block are currently dependent on the area containing this block. If you override those permissions here, they will not match those of the area." By area I take it means the Header Nav area which is what the autonav block resides in, but how do I edit the permissions on an area? That is set up in the template itself.

Sorry if these are dumb questions but I'm relatively new to c5 and don't want to balls things up!

Many thanks,
Tony.
brennaH replied on at Permalink Reply
brennaH
I was having the same issues and then, when I clicked in an area to add a new block, there is a permission tab that allows you to set default permissions for the area.

Hope that helps!
nathan replied on at Permalink Reply
nathan
I'm having similar problems, I've managed to disable the ability to edit the existing autonav block but I can't disable the ability to add another block (of any type).

I'm not sure what I'm doing wrong but it seems like the permissions that restrict adding block types to an area are either not being saved or not being read at all.

I'm running out of things to try here, I've looked at this post:

http://www.concrete5.org/community/forums/customizing_c5/permission...

and this is the same issue, no matter how the permissions are applied to an area the editor user is still able to add every block type regardless of the restrictions set in the "Add" section of the permissions window.

I've even tried this on a fresh install in case there was an issue with the current install but still no joy. There has to be a simple explanation for this but spending a day trying to get it working is becoming very frustrating.

PS: frz, I don't think this is as intuitive as suggested because there are quite a few posts regarding the same issue, the sooner you can put this into a screen cast the better ;) I really hope I'm doing something wrong and it's not a bug...

Cheers.
nathan replied on at Permalink Reply
nathan
Hah, so typical, as soon as I post the problem I go right back and fix it...

How? (good question)

I'm not entirely sure but it seems to have something to do with the order of how you add the permissions.

I managed to get it working by using the "inherit page type default permissions" on all of my existing pages.

Then I went back to defaults (as admin) for the page type and reset all of the permissions on each existing block and the add to block permissions tab.

Saved the default, logged in as editor and the editor can no longer add additional blocks to the header nav or sidebar nav, and they are restricted to which blocks the can create in the main area.

So, the permissions do work but without any formal documentation you might find yourself banging your head against the wall for a few hours at least.
powermick replied on at Permalink Reply
powermick
I surely did not understand the manipulation was done, but for me it does not work.

can you explain in detail how to restrict the addition of a type of block in Area
hockeyshooter replied on at Permalink Reply
hockeyshooter
Our C5 site has been running for a while and I turned on Advanced Permissions only recently (with the intention of allowing non-admins to change their own password). I've since turned it off, but now no one in the administrator group (ie: no one at all) can see the left-side menu in the Dashboard - meaning the site has been rendered next to unuseable. Any idea how I can fix this - or will I have to restore the entire site from backup?

From this thread, I get the feeling that Advanced Permissions is currently a recipe for disaster.
Maynar replied on at Permalink Reply
Maynar
I'm using it from the start and no issues what so ever!

Works perfectly, I misunderstood the super user model (like it existed), but other than that it works like a charm.
hockeyshooter replied on at Permalink Reply
hockeyshooter
Understanding is half the problem - especially when there's no flamin' documentation.
Maynar replied on at Permalink Reply
Maynar
Not entirely sure what you meant, but if you don't understand the advanced permissions model you go to this topic where I have posted some user documentation which also covers the advanced permission model:http://www.concrete5.org/community/forums/documentation_efforts/use...
hockeyshooter replied on at Permalink Reply
hockeyshooter
Thats great - thanks for making the effort.
frz replied on at Permalink Reply
frz
is not a good idea.

generally one is encouraged to build a site in either advanced permissions mode or simple permission mode. switching between them would certainly be a recipe for disaster.

advanced permissions are perfectly stable, in fact, they were built before the simple permissions mode which is really just a hack on top of them.

the biggest challenge you'll find is that a site that is built out with simple permissions and gets put into advanced permissions mode might have weird settings applied to blocks and pages as concrete5 tries to figure out what to do.

sounds like that's what happened to you.

I'd suggest putting it back in advanced permissions mode and just cleaning up all the settings when you're logged in as admin.
AlbertPotato replied on at Permalink Reply
AlbertPotato
If I've already switched back and forth, is there a way to clean things up? Or, what "funkiness" should I watch out for?