I have 6 different vocabularies, 2 of them are private and only should be seen by administrators. When I turn on list for any of the terms (or a vocabulary default) in the anonymous TAC profile, anonymous users can see all terms assigned to the node, regardless of what vocabulary the terms are from. I've uninstalled TAC and rebuilt the TAC profiles several times but this keeps happening. In the meantime, I've just turned list off for all taxonomy terms, but I would like anonymous users to be able to view at least some of the terms.

I'm using version 5.x-2.0, with PHP 4.4.9, MySQL, and Druapl 5.22. I'm not using any other access control modules.

Comments

chromix’s picture

Version: 5.x-2.0 » 5.x-2.x-dev
Assigned: Unassigned » chromix
Status: Active » Reviewed & tested by the community

I was able to fix this by swapping line 377 and 378. Seriously, it was that easy. So this...

    return $return;
    }

...becomes this:

    }
    return $return;

And then the module works as intended. Apparently not very many people must be using the latest version or else I'd feel someone would have picked up on this by now. Either way, hopefully this helps someone else out there.

xjm’s picture

Confirmed, that's the bug that brought down 6.x-1.1.

xjm’s picture

Status: Reviewed & tested by the community » Fixed

Committed in: http://drupal.org/cvs?commit=396752. I guess this is more properly a duplicate of #746548: typo results in create permission being ignored. In any case, fixed now.

Status: Fixed » Closed (fixed)

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

slapierre’s picture

Hello,

I'm having the same issue, only it should be fixed from what I read here!

Any idea about what can cause anonymous users to see a taxonomy term even though the List option is set to unchecked for them?

thx

xjm’s picture

#5: Are you using the current 6.x-1.x-dev build? If not, give that a shot. There's another fix that's not yet in a release.

If you are using a 5.x version of the module, it is unfortunately no longer supported, but you should try the 5.x-2.x-dev build in that case.