What's the <none> option functionality? [#375672]

Hello, I just installed the module and ran into problems.

My site structure has limited access only to stories, all pages should be visible for everyone. Because of this reason, my access vocabulary isn't applying to anything but the stories.

Regarding the stories, access control works fine. However, no pages show for anyone since they don't have the access vocabulary! One would imagine that the <none> option in my scheme would mean that if a term from this vocabulary isn't defined in a node, then the node would show. Not true. :(

I think that the reason for this is my Domain access module, and the multiple node access patch that I had to make in order to get these two modules working together. The patch replaces Drupal's default OR logic with AND logic regarding access control - meaning that both Domain access and TAC Lite would have to give a permission for the pages to show. Without this patch, the permission Domain access gives would be enough and nothing else could be restricted.

Wouldn't want to add the unnecessary vocabulary to pages, can someone think of another option?

Comments

Comment #1

Dave Cohen commented 17 February 2009 at 21:44

I think you pointed out the issue. You've changed things to require AND logic, and you're not tagging the pages. With Drupal's default OR logic, the <none> option would allow users to see the content, as you would expect. So, everything's working the way you've configured it.

An option would be to define your own content type in a module and use it instead of page. Your module could then implement hook_access, and use PHP logic to control who can see what.

Some patches have been proposed to allow modules to alter the node_access data. This would help in your case. Consider using that patch instead of the AND logic patch you applied. Sorry I can't find the link to that issue right now.

Comment #2

mnordstrom commented 18 February 2009 at 10:34

Thanks for your answer, have to think what's the best option to get around this issue (maybe hooking the pages to have the "everyone" item of the access vocabulary automatically and not visibly).

Anyway, the "All" option discussed in other issues would solve this problem easily. Then I could associate the vocabulary with the page structure to grant access, too. This "all" feature wouldn't have to be on automatically (in response to the problems), but an additional option for people to switch on. Oh well, not going to happen quickly anyway, just something for you to consider about. :)

Thanks for the module in general, great work!

Comment #3

jeffreyvddb commented 29 September 2010 at 10:53

I've stumbled upon this issue also. Since the last post was posted on February 18, 2009 I'm wondering if there is a solution for this issue. If so, could you point me in the right direction? Thanks!

Comment #4

Dave Cohen commented 29 September 2010 at 16:48

All I can tell you is tac_lite is designed to work with drupal, and not drupal patched to do node_access in a completely different way.

So if you guys come up with a patch you're welcome to share it here. But I don't plan to include it in tac_lite if it makes it more complex or harder to maintain.