I just installed the Content Access module, and set it up so that only Admin and auth users could view a content type called "Member Article." I logged out, and typed in the article URL as an anonymous visitor to test, and found I could access it fine. Thoughts?

Thanks,
Sam

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented

I've just tried it again, and it works for me..
Have you tried creating a new node of this type - does it work for the new one? Are you sure you have no view access for anonymous users enabled?

enboig’s picture

enboig commented

it don't work for me either. I am using also "Taxonomy Access Control", but is not active for the "page" node.

I have set "per node" permission, and disabled everything for a node and anonymous user; but the anonymous user have access to the node. I created a new node in order to check if this was a problem, but the problem continues; I have "rebuilt permissions" but the problem is still there.

any hint?

thanks

fago’s picture

fago
Primary language German
Location Vienna
commented

so you have this problem with per content-type permissions and not with per node permissions, correct?
@enboig: try if disabling tac helps.

enboig’s picture

enboig commented

At last I had to forgot about Content Access, I created a new taxonomy just for Pages, and use that to tag content public or private using Taxonomy Access Control.

Now works, but it is a pity you cannot use these two modules together.

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Fixed

They should work together. I don't know which priority TAC is using, but if it uses the default 0 as content access per default does, then they should work together, which means:
If one module grants access to a node for a user, it will be able to access it.
If none grants access, the user won't be able to access it.

Fine that it's working now.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)
belmondo’s picture

belmondo commented

Thanks for the comment above (#5) that confirms TAC (Taxonomy Access Control) and Content Access (CA) DO work together. This comment should be included in the readme for the CA module together with some guidance on integrating with other access modules. I had some initial problems using both at the same time on my D5.7 site but now they do work beautifully by:
1. leaving the Content Access priority set at 0 (the default)
2. making sure every post has a term assigned from the vocabulary I use to control access with TAC and setting the required permissions with TAC.

Before I implemented this second step I had 'unassigned' posts that I wanted anonymous users to be able to access but CA denied the access and TAC wasn't granting it so it wasn't working as I wanted.

I use Content Access to control access to nodes with downloadable files attached and I use TAC to control access to all other content. Content Access is a great module and together with TAC I consider it the gold standard for access control in Drupal.