Hi Mike,

It's been a while since I used Tax Access -- much preferring the organic groups module to set aside private content these days -- but from what I remember, the TA module works in a permissive way in that if any term associated with a node can be viewed by the public, then that node is treated as public. In other words, you can strict access only by limiting tagging to the restricted term(s).

That part is obvious. What's not as obvious is that books are treated as one big document, comprised of strung-together nodes. As such, you might have one book page somewhere that is not restricted by TA, and that makes the whole book visible.

Just a guess, but the problem you mention resonates with this new post about re-thinking the book module: http://drupal.org/node/65319 .

I hope this is of some help.

Laura

pingVision, LLC 4450 Arapahoe Ave, Suite 100 Boulder, CO 80303

www.pingv.com 303.415.2559 inquiry@pingv.com

On May 24, 2006, at 3:51 PM, Mike Hartman wrote:

I recently upgraded to 4.7 and I’m still getting the hang of Drupal.

I’m also using the Taxonomy Access module to restrict access to certain nodes by user role.

I’m using the book module for one area of the site along with the Taxonomy Access module to make them viewable for only certain user roles. In permissions I have everything pertaining to the book module such as “create book pages”, “edit book pages”, etc turned off for a user role. But when I log in as that user I still see the “view” and “edit” tabs on the pages of the book and I’m still able to click on the “edit” tab and make changes to the book page. While trouble shooting this I turned off every permission setting except “access content” for that user role and I still see the “vew” and “edit” tabs when logged in as that user.

I’ve also noticed the “authenticated user” role will effect the other roles I’ve created so I unchecked all permissions for that role as well with no result.

Any ideas?

Thanks

Mike Hartman

-- [ Drupal support list | http://lists.drupal.org/ ]