Fork me on GitHub

PostCalendar and Permissions on category level?  Bottom

  • Hi!

    These permissions are driving me crazy! Somehow I don´t quite understand how it works. My latest problem is this:

    I´m trying to give different user groups permission to add events in different categories.

    For example Users in "GroupA" should have sufficient permissions to be able to add events in "CategoryA" and users in "GroupB" should be able to add events in "CategoryB"

    My current config lokks like this: GroupA|PostCalendar::|.*|Delete

    With this configuration GroupA has access to all categories, which I don´t want.

    Does anybody know how it should be?

    Regards Mats
  • If you click on the header of the permision table it'll bring up a window with all the modules and blocks permision scheme to work with. Doing this you'll see that PostCalendar has 2 permision schemes, one basic and one for categories... the category one looks like this
    PostCalendar::Category | Category Name::Category ID

    I have no idea why it seems to ask for the same information in 2 different ways in the second part especially since PostCalendar admin area does not expose the category ID so you'll have to check the database table pn_postcalendar_categories to see it.

    Although, it can't hurt to try it with just the name...

    --
    Under Construction!
  • Hi!
    I have already tried the configuration you are describing. Have a look at the following picture. I have been trying to get it to work for group "Ledare A-Lag" and the category "A-Laget" with category ID 2. But still users in the group "Ledare A-Laget" can add events to other categories?!

    PostCalendar Permissions

    Can anyone see what is wrong?

    Regards Mats
  • I am not expert, just started on postnuke myself, but let me share some things I have learned as of late, doing the same things you are doing.

    Think of the actual permission itself as access levels, and that they stack on one another. So "none" is at the low end, and "admin" is at the high end, an it goes from low to high in order.

    the Permission level "delete" is lower to only "admin" which gives that group a lot of abilitites, not just to actually delete something.

    To me, it seems line 7 is right, but at line 8, you are taking away any permissions, you are granting it to them. I would modify that to just "read".

    hope that helps.

    I could help but notice that you gave unregistered users "admin" access to something...you realy should change it. If I were you, I would bring it down at least 2 slots, to "add", but that is just me :D
  • ankah

    To me, it seems line 7 is right, but at line 8, you are taking away any permissions, you are granting it to them. I would modify that to just "read".


    Wrong way, goes from bottom to top so 7 would over-ride 8.

    The pic is no longer there but it looked right to me. I think the problem is that PC simply does not support this kind of permisioning... the detail scheme is likely for viewing not adding... at least I could not find it in the code.

    However I'm going to have need of such a feature myself fairly soon, if I can manage it I'll make the modification available here.

    --
    Under Construction!
  • Hi, teh reason why you didn´t see the pic is that I close down my PC at about 23:00h CET.
    I´ve tried all possible combinations but I cannot find what is wrong. About the unregistered users having access to the calendar was a mistake. I tripped on the keyboard. :-/

    Thanks!

This list is based on users active over the last 60 minutes.