I have created several roles in relation with taxonomy terms. For each taxonomy term, I set the permissions so that only the administrator and the dedicated role are allowed to use the term. However, neither the administrator nor the dedicated user are not able to see the term and no other user can see it.
However, if I set the permission using the username instead of the role then it works but I have many users so using the username is not possible, I need to be able to use the role permission.

Comments

vdeparday’s picture

vdeparday commented
Title: Permissions set by role don't have any effect » Permissions set by role is working backward: allowed role are actually the restricted one

So I found out why I thought it was not working. When setting the permissions by role, it is written "Allowed Role" so you would think that the role you check are the roles that are allowed to see the tags. But it is actually working backwards, the roles that are checked are the roles that cannot see the tags.

Either you should change the wording or you should make it so that the checked role are actually allowed and not restricted.

I think the second option (allowing role rather than restricting) would make more sense because as it stands, every time you add a new role you have to go through all the taxonomy to restrict the tags to this new role.

vdeparday’s picture

vdeparday commented
Title: Permissions set by role is working backward: allowed role are actually the restricted one » Permissions set by role is working backward: allowed roles are actually the restricted ones
misc’s picture

misc commented
Status: Active » Closed (works as designed)

This work as designed - Roles that are allowed to use the terms can refer them.

dshields’s picture

dshields commented
Status: Closed (works as designed) » Active

I would have to agree with vdeparday..

Where it reads "Select a role to allow all members of that role access to this term", one would expect any roles to have access to this taxonomy term.

In my experience, this results in the exact opposite of what is described.

When I check "user role 1", every user on the site is granted access except for those users who have the "user role 1" role.

dshields’s picture

dshields commented

By checking "authenticated user" (which is essentially a parent user role for all user roles), all user roles should be checked by default, as is the behaviour on drupal's permissions configuration page.

If "authenticated user" is unchecked, then each child role which is checked, to use my previous example: "user role 1" should be given access to this taxonomy term while unchecked user roles should not.

Are we not clearly understanding this functionality?

dshields’s picture

dshields commented

This actually works properly, if the module is hacked as described here.

If anyone has any other feedback, I'd love to hear it.

misc’s picture

misc commented
Status: Active » Fixed

Mark this as fixed as #701746: Permissions settings have no effect is committed to latest dev.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.