I am using the taxonomy access modual and I made a taxonomy "hive" and under that I made "buzzbuzz". I want anything labled with "buzzbuzz" to only be viewable by certin roles, so i left "view node" under "hive" and "buzzbuzz" unchecked for the roles that I don't want to see the info posted with "buzzbuzz" as a lable. But when I sign in with my generic user the user can see all the content that is labled with "buzzbuzz", so it is not working.

I was told that the only way to stop this is to uncheck "promote to front page" in the post. I just though that might be something to fix.

Comments

keve’s picture

keve commented

"promoted to front page" has nothing to do with TAC.
The problem is something else.

Do you use latest version of TAC? What is your version?
// $Id: taxonomy_access.module,v 1.47.2.15

Those the given node is assigned to other taxonomy terms, apart from "buzzbuzz"?
Because in that case there is an OR operation between permissions.

bdmp’s picture

bdmp commented

I am using the latest version. You are right. That did not fix the problem. The node is only associated with "buzzbuzz" so there should be no taxonomy conflict. I asked about this problem on the irc channel and someone told me they had the same problem and they fixed it by having the nodes not promoted to the front page.

I thought that the confilict might come from the fact that it is a forum, so I made a book page with "buzzbuzz" but that is visible too. I am not sure what is causing the problem. Any suggestions?

keve’s picture

keve commented

I am using the module without any problem on my commercial site (with 8 levels of permissions).

Did you activate the module on /admin/settings/taxonomy_access?
Did you have any other access module installed before (eg.og)?
Read troubleshooting section in install.txt.

bdmp’s picture

bdmp commented

I had simple access enabled and now I unenabled it and taxonomy access control is still not working so all my private stuff in now public so I gotta get this working. The other sections like the forums seem to work fine. What am I missing?

bdmp’s picture

bdmp commented

let me get this straight. If the box for a taxonomy term is unchecked under "category permissions" then that taxonomy term should not be visible right? It seems that mine is not working, but the forums and stuff are fine.

bdmp’s picture

bdmp commented

I think I have misunderstood what this module does. I thought that if I made a category term private and made a node and associated that term with the node then the node would be private, but it appears that it only hides the term being associated with that node. Meaning anyone can see the node but only roles that have permission to see "buzzbuzz" can see that the node is associated with "buzzbuzz". It does not actually hide the node itself, right? Is this true?

keve’s picture

keve commented

Try: Truncate table node_access, then go to admin/settings/taxonomy_access, and deactivate then activate module. This will completely regenerate node_access table.
(Content access is controlled by 'view' permission.)

> taxonomy term should not be visible
This is controlled by 'list' permission. Did you patch taxonomy.module right?

keve’s picture

keve commented

I cannot regenerate this bug.
4.6.5: I use it without any problem on my commercial sites.

Silver123’s picture

Silver123 commented

I've got the same problem, but no idea how it can be solved.
I tried truncating node_access, but taxonomy_access starts again with the same setting. Don't know, where they come from!

keve’s picture

keve commented

Can you please write, how to regenerate this bug on a fresh install?

Can you check table node_access for that nid. What are the grant_view values for the dirrerent roles? Is it all 1 (viewable)?

keve’s picture

keve commented
Status: Active » Closed (fixed)

TAC for Drupal 4.6 or 4.7 is no longer supported.
Try using latest 5.x-2.x-dev version, the module has been totally rewritten.