Terms not listed in the categories

First, your post is very confusing because I think you have the terminology confused.

Categories and Terms are the same thing. Categories go into Vocabularies. From your SQL, you have four categories going into two vocabularies.

With that out of the way, the second thing is that you don't have view permissions set for those categories, that's why they're not showing up. Even if someone has add/delete/whatever access, it's not going to be viewable when they don't have view permissions, that's the way it's supposed to work.

Also I wanna say thanks for the database file, that helped alot.

That checkbox comes from the database, so I don't see how it could be getting checked.

For a specific example, try anonymous users (role 1) for pb_term1 or pb_term2, view shouldn't be checked in either place (as it's not set in the DB).

So the anonymous user shouldn't be seeing this category, because view isn't checked.

Without view, the user shouldn't even know the category is there.

Yeah that's not my code, that's a core function.

But are the categories showing up now that you have view enabled?

No that's entirely right. View isn't checked, so the anonymous user cannot see those categories. That's the way it's supposed to work.

Yes enabling the module removes that last bit of SQL you posted. Disabling the module inserts it. That's what it's supposed to do, override taxonomy_access or any other node based access.

Could you post the SQL again?

I have an issue that I think is similar so I won't file a new report.

What I'm seeing is that when I'm logged out, none of the terms of the Employment vocabulary show. This is expected as anonymous user does not have view permission in the category.

However, when I log in as test_user, an authenticated user, he cannot see any terms under the Employment vocabulary either.

When someone who is a programmer_op role logs in, they can see the terms under the Employment category just fine as can the admin account.

I have no idea whats happening as when I look in the database permissions seem ok so all I can think of is somewhere authenticated users are getting taxonomy access based on the anonymous users settings, at least in some places as an authenticated user (so far as I know, it might have recently gotten messed up with a cvs version I loaded up) is able create nodes in the User Submissions vocabulary under the Submissions term.

I am attaching the relevant sql. The user table has been truncated and passwords cleaned up for obvious reasons.

I'm interested in similar desired output: Category A is public, anonymous can access, and Cat B is private, anonymous can't access, I don't want public/anonymous to see Cat B even exists.

I turn navigation off for anonymous users, registered users enabled navigation.

When anonymous users go to category A, navigation is displayed, listing Cat B. Anonymous users can't access Cat B, but it is listed in navigation.

Understand navigation is separate from this module; the two are related. Ensuring privacy to some taxonomy would include not seeing that it exists?

Yes however that's the navigation module, we have no control over that. If navigation was using the taxonomy.module functions to find the terms it wouldn't be there, but it seems they're not so you'll have to ask them to add support for taxonomy_access.

Actually, it appears that taxonomy_get_tree should drop categories from the list if they don't have view permission; however, there appears to be a bug in taxonomy_access itself, which prevents it from getting the correct role IDs for a particular user. Specifically, this code in taxonomy_access:

  if (isset($user)) {
    $user_object = user_load(array('uid' => $uid));
  }
  else {
    $user_object = $user;
  }

should probably read:

  if (!isset($user)) {
    $user_object = user_load(array('uid' => $uid));
  }
  else {
    $user_object = $user;
  }

When I make this change in the module, I can finally create a private forum that isn't even visible in the forum list, if the user doesn't have a role with the appropriate permission assigned for the forum.

Thanks! Commited to CVS. I was having a hard time figuring this one out. That should fix the original poster's problems.

Terms and Categories are the same thing, what do you mean exactly?.

That's not a bug, Taxonomy Access Control doesn't control access to vocabularies. Just Categories. So while the category isn't showing up, the vocabulary always will because TAC doesn't control that at all.

No, you can't vocabularies either. This module does not control vocabularies. They are always shown. This module does not touch them.

Sorry, it should read "You can't add vocabularies either"

The issue I was seeing was fixed in the most recent CVS verstion. Sorry it took me so long to try it out.