Greetings beerlings,

I cannot get this module to work for me.

- Installed and activated the module.
- Set access on single content type to administrator only (all check boxes admin only).
- Anon users can still access node's of respective content type.

I also tried turning on the node level permissions and set the node to admin only with no luck.

This seems so easy to setup. What am I missing?

anon role core security settings are "access content" only...

Thanks,

RL

CommentFileSizeAuthor
#5 anonymous_issue.png13.16 KBidcm
#5 anonymous_issue_settings.png19.88 KBidcm

Comments

drupal_jon’s picture

drupal_jon commented

Hi,

Try going to Administer -> Content Management -> Post settings (/admin/content/node-settings), and then click the button to "Rebuild permissions". That might take a little while if you have a lot of content on your site.

vincetingey’s picture

vincetingey commented

Hello,

I'm getting the same problem with the latest version of Content Access (6.x-1.2 stable) and Drupal 6.15. I've tried rebuilding permissions, uninstalling content access, reinstalling... don't know whats going on but I cannot restrict content to anonymous users...

vincetingey’s picture

vincetingey commented

I fixed my problem.. it had to do with increasing the node grants priority to 1 from 0. I'm also using taxonomy access module as well as content access on my site. Funny tho I had no taxonomy access settings (or even taxonomy) for the content type I was trying to restrict via content access...

salvis’s picture

salvis
he/his
commented

You should not change priority unless you really understand what you're doing.

To begin to understand what you're doing download the current Devel module, enable the Devel Node Access (DNA) module, locate the "Devel Node Access debug mode" checkbox at admin/settings/devel#edit-devel-node-access-debug-mode, and turn it on. (You may have to manually put the two DNA blocks into the Footer region if they're not visible.) This will show you how the various node access modules interact with your nodes.

If you need help, pick ONE node that is misbehaving, look at it using an account that can see the node (and that should NOT have access if that's your problem), and attach a screenshot of the DNA information.

idcm’s picture

idcm commented
StatusFileSize
new anonymous_issue_settings.png19.88 KB
new anonymous_issue.png13.16 KB

I experienced the same issue after installing taxonomy access. I changed the priority for the one CT from 0 to 1 as an experiment and it worked. DNA showed that the node was viewable by anonymous even when the content access said it shouldn't.

TimJFowler’s picture

TimJFowler commented

Drupal 6.17
Content Access 6.x-1.2

I am having the same issue. Anonymous users can view "member-only" node type with "Role based access control settings" all un-checked for anonymous users. "Rebuild Permissions" had no apparent effect.

salvis’s picture

salvis
he/his
commented

The answer is still the same as #4. We need the block that #5 did not show...

TimJFowler’s picture

TimJFowler commented

Thanks!

Installing the Devel module clarified the priority interaction between different node access modules and I was able to resolve the issue.

salvis’s picture

salvis
he/his
commented

Great, thanks for letting us know!

idcm’s picture

idcm commented

@timjfowler - how did you resolve?

TimJFowler’s picture

TimJFowler commented

I increased the "member-only" content node grants priority to "1" which gave it top priority. That fixed the issue.

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented
Issue summary: View changes
Status: Active » Closed (outdated)