Hi,
i have a simple problem. I installed the module and after configuration I can still see the node that is supposed to be hidden.
I tell you what i did:
1. I added a Scheme with all the vocabluary that I have at /admin/user/access/tac_lite/scheme_1
2. I marked "view, update delete"
3. I marked "Keine" = "no rights for all rolles
4. I tried it as a guest (within the profile the users have also no rights) and I can see the node.
What I cannot see is the taxonomy term. If I allow a single taxonomy term and another not I can see this particular term under the node. But I thought TAC_Lite can hide full nodes not just the taxonomy terms under the node.
Did I get this wrong?

Comments

Dave Cohen’s picture

Dave Cohen commented

tac_lite does not hide nodes. Instead, it makes visible nodes that a user would otherwise not see.

So disable tac_lite, log in as guest. Can you see the node? If so, its one of drupal's permissions or some other module which is allowing you to view. Fix that, then re-enable tac_lite and everything should work.

chris_bbg888’s picture

chris_bbg888 commented

ah ok, my purpose is to hide nodes on the basis of taxonomy. hmmm which module would do that?

Dave Cohen’s picture

Dave Cohen commented

That's just not how node_access modules work in Drupal. Change the permission so non-admins cannot view the nodes, then use tac_lite to make them visible by taxonomy.

chris_bbg888’s picture

chris_bbg888 commented

ok, I see your point. maybe you can help me again. I read the readme very carefully but dont get it running.

1. I disable that guests can read all nodes.
2. I double check: guests cannot read any posts/nodes
3. I enable TAC_lite
4. I add there all my vocabularies
5. I mark in the module "view, delete, edit" and also all vocabulary for the role guests.

FYI: the node I try to see has a taxonomy term attached.

Result: I still cannot see the node as a guest.

I chose guests on purpose as there cannot be a conflict with the settings you can do for a user with your module. I must do any mistake, but I dont see what. Thanks

chris_bbg888’s picture

chris_bbg888 commented

I mean the module is supposed to work, isnt it? so I guess I make a stupid mistake. what you that be?

Dave Cohen’s picture

Dave Cohen commented

In the devel module, there's a devel_node_access.module. Enable it, and then configure the block it provides to show up in your page footer. Then when you view a node it will show you the node_access table entries for that node. That might give you some hint of what's wrong.

It can be tricky because Drupal permissions can be complicated. It only consults the node_access table if no module explicitly grants or denies permission.

chris_bbg888’s picture

chris_bbg888 commented

ok thanks dave, thats a big help.
as I result I think the module is not working for my purpose. I write this for all the other that might have a similar problem

here are my findings

1. I have to tick in the admin/user/permissions read content, otherwithe the TAC wont do anything. So far so good
2. If I tick "read content" I can further configure "update" and "delete" of a node with the TAC. For "view" it doesnt work. If I want a person not no be able to view a node I would have to not tick "read content" (in the permissions). But that would mean that I cannot edit "update" and "delete" again.

Many thanks and best regards

kmillecam’s picture

kmillecam commented

Dave, so you're saying you should first edit the user permissions and make sure the role in question (anonymous user in this case) does not have the "access content" permission?

And by doing so, you can use TAC Lite to override the node module and grant view access to the tagged node to anonymous users?

I'm just trying to get clarification because I too have misunderstood how this module works.

Thanks,
Kevin

Scott J’s picture

Scott J commented

Yes, I think that simple statement "tac_lite does not hide nodes. Instead, it makes visible nodes that a user would otherwise not see etc." deserves being put on the front page of the module in LARGE LETTERS.

Actually, no, put it on the front page of drupal.org as I think that it would save much confusion, frustration and disappointment for would-be Drupal users.

Dave Cohen’s picture

Dave Cohen commented
Status: Active » Fixed

Added some text to this effect to the project page.

Status: Fixed » Closed (fixed)

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