Loading...
 
Skip to main content

Features / Usability

Forum List Topic List

 
Thread actions
Print this page
  • Print all pages

    • Permissions level bug in 1.8RC3

    Posted by joelg

    I seem to have found a bug in the Group Permissions configuration.😢
    I can only create one Level on top of the four defaults. I create a level (eg Public1), I assign some permissions to it, it seems to work. Then I create another level (eg Public2), and lo and behold! Public1 has disappeared from the dropdown lists of levels!

    This must be a bug.

    In addition, I would like to say that I find the way the permissions work incredibly confusing. The reason I want to create different "public" levels is that if I assign "basic" to my anonymous users, then it actually assigns ALL the basic permissions to them, including those that belong to features which I've not turned on!

    In addition, the list of permissions for the group is unbelievably long and tedious.

    Moreover, there is no way of easily viewing the permissions assigned to a Level.

    IMHO, what is needed is this:
    1) groups inherit permissions from one or more levels; the groups permissions only show the levels, not individual permissions
    2) a levels administration screen where it is possible to see at a glance what permissions are atatched to a level

    Any takers?

    All the best, Joel

    Reads: 1595
    Posted by Damian Parker

    Joel,

    Personally I dont ue the permission levels. I prefer to just use the groups themselves and have a serious of groups inheriting from each other.

    Using this method its much easier IMHO to sort out permissions for each feature, by clicking on the permission feature groups and checking what that group needs.

    Just a couple of thoughts there

    Damian

    Posted by joelg

    > Damian:
    > Joel,
    >
    > Personally I dont ue the permission levels. I prefer to just use the groups themselves and have a serious of groups inheriting from each other.

    I'm inclined to agree with this comment. I find the whole way permissions and groups are laid out in the groups management screen inherently confusing and from what you say there is no clear logical distinction between groups and levels anyway, so one of them is certainly redundant.

    What I'm really trying to do is to find some way around the incredibly irritating "feature" which I mentioned in my post, which is getting everything assigned from "basic" (for example) including things you don't want (violates the basic security principle that "everything not explicitly allowed is forbidden).

    I'll try your suggestion anyway.

    All the best

    Joel

    >
    > Using this method its much easier IMHO to sort out permissions for each feature, by clicking on the permission feature groups and checking what that group needs.
    >
    > Just a couple of thoughts there
    >
    > Damian
    >


    Posted by joelg

    > Damian:
    > Joel,
    >
    > Personally I dont ue the permission levels. I prefer to just use the groups themselves and have a serious of groups inheriting from each other.

    I'm inclined to agree with this comment. I find the whole way permissions and groups are laid out in the groups management screen inherently confusing and from what you say there is no clear logical distinction between groups and levels anyway, so one of them is certainly redundant.

    What I'm really trying to do is to find some way around the incredibly irritating "feature" which I mentioned in my post, which is getting everything assigned from "basic" (for example) including things you don't want (violates the basic security principle that "everything not explicitly allowed is forbidden).

    I'll try your suggestion anyway.

    All the best

    Joel

    >
    > Using this method its much easier IMHO to sort out permissions for each feature, by clicking on the permission feature groups and checking what that group needs.
    >
    > Just a couple of thoughts there
    >
    > Damian
    >