All the docs have to say about what "Ignore" means in the context of this module is:

"VIEW, UPDATE and DELETE have three options for each term: Allow, Ignore, and Deny.
Indicate which rights each role should have for each term."

What I'm hoping ignore means is that it uses the core content type access control.

I'm hoping to use TAC to allow anon users to see one particular content type, but I'd rather manage most of the content access in admin/user/access

That is, I'm hoping that I can install TAC, go to anon user role, allow a specific term and be done (letting core access control the rest as I had already set it up).

I'd love a reply here, and suggest that such a clarification of what "Ignore" means is added to the docs.

-P

Comments

keve’s picture

keve commented

Please read the help page of TAC (I think /help/taxonomy_access) and the readme.txt.

ptone’s picture

ptone commented

I had read through these, and still feel the docs could use some clarification.

I'd suggest the note in the readme about other node access modules being OR'd with TAC be promoted to the help screen from the readme, with the further clarification that while such OR'd permissions may permit access to the node content itself - TAC's default to deny on ignore will still block use of term pages (taxonomy/term/9, resulting in a 404 not a 403). TAC also controls access to the API call taxonomy_get_tree independent of any content access.

I'm posting this for anyone who runs into the same confusion about content vs taxonomy access. The logic is clear once you get it, but there are several pieces of the puzzle.

general need’s picture

general need commented

Agreed, I am not 100% sure what 'Ignore' implies. The docs do not state it at all.

BioALIEN’s picture

BioALIEN commented

From experimenting with this, "Ignore" seems to work more like "Invisible". It stops access to the content that would otherwise be accessible by default. This is using the HEAD version of the module on D6, so it could be a bug.

I agree that precise and accurate documentation is needed.

yhager’s picture

yhager commented

Maybe this one explains it http://drupal.org/node/68387

yhager’s picture

yhager commented

Here is a fine explanation from the module author.
http://drupal.org/node/77416

xjm’s picture

xjm
she/her
Primary language English
commented
Status: Active » Closed (fixed)