Page 1 of 1

Managing backend user right more detailed

Posted: Thu Jun 05, 2014 7:44 pm
by Guido
Hi,

As I'm completing a site for a cliƫnt, I'm in the proces of setting up an 'editing user'. I found that although you can change a lot in the permissions, still not everything can be modified in detail.

That's why I'd like to use the module_custom option to create custom templates. For instance, in the 'fields' tab of the CGCalendar module I've modified the template to show only the message that no fields can be created.

However, I would like this template to distinguish between users or user groups. So basically an if/else statement that shows a short 'no you can't do this message' when a certain user or a user from a certain group is logged in, but shows the normal template when an admin user is logged in.

EDIT: For the CGCalendar module, I found that there is an option to show only basics in the standard permission tab.

I've checked the login.php file to see if there was a variable I could use for this if/else statement, tried a couple of things but unfortunately I'm no programmer so I got stuck.

If anyone has any tips, thanks in advance.

Re: Managing backend user right more detailed

Posted: Thu Jun 05, 2014 9:22 pm
by Guido
Diving in a little deeper, I came up with an idea that might be useful in the future:

Every edit/display page of every module has it's .tpl file right? What if you could set rights for editor/admin/whatever per .tpl file, beside managing permissions within that file? I mean, sometimes you just don't want end users to be able to edit categories, hierarchy or whatever at all. Since they're usualy ordered like this, you could make a 80% filtering just by doing that and setting permissions per group could be really fast...