I have two vocabs for my photos, year and and access. Year makes no difference for control purposes and access is either public or private. i have one public album and one private. If i set all years to be viewabale by anonymous users they can see public and private albums. If i set all years to be not viewable, they cannot see either. It seems to be completely ignoring the vocab i want it to be paying attention to. how are multiple categories suppose to work? any way to make the one i want the primary one?

Comments

Jedi Stannis’s picture

keve’s picture

Category: bug » support
Priority: Normal » Minor

The patch above was commited to TAC couple of month ago.
Please always use latest tarball.

In case of nodes with multiple categories, there is a logical OR operation between permissions, if the user have e.g view permission for any of the terms, s/he will get view permission for the node.

munga’s picture

Version: 4.6.x-1.x-dev » 4.7.x-1.x-dev

this is related with my question here

is there any way of using taxonomy_access in this scenario ?

I think the problem is related with the use of checkboxes instead of a drop down menu with
three options (access/no access/don't care). This way it would be possible to specify for
each term a positive or negative condition or ignore the term in relation to access restrictions.

It make sense to think that if a node is associated with a term with no view access, the node should
not be visible even if it's related with an other node with view access...

Moreover I think it would be nice to add a bit of JS (similar to the general setting page) to collapse
multiple rows.

thanks :)

keve’s picture

Logical OR operation means, that in case of nodes with multiple categories, if you give user permission to any term, the permission is granted.

That is: If you give permission for Vocab1:A the permission is granted, even if it has no permission either Vocab2:private or public. In this case you need to set permissions for Vocab2 only (which should be the vocab to control access), and you should not set any permission for terms in Vocab1. (leave it unchecked).

You are right, i am already working on a new version of taxonomy_access, where there is dropdown box: allow, deny, ignore.
Also there will be an option: Order Allow,Deny or Deny, Allow. Similar to Apache.
Please check back some time.

keve’s picture

Status: Active » Fixed

For the new permission system w/ dropdown selections 'Allow/Ignore/Deny', check cvs version of TAC.

I also made JS collapsible the vocabularies on the category permission page.

Anonymous’s picture

Status: Fixed » Closed (fixed)