Posted by proindustries on May 7, 2009 at 2:33am
Jump to:
| Project: | Nodeaccess |
| Version: | 6.x-1.3 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (cannot reproduce) |
Issue Summary
Guys - hoping I'm missing something here...I have nodeaccess installed on a site where I don't really want the general public viewing a custom user guide for the CMS. So I "granted" permissions on that page so there are no pages for anonomous, read access for authenticated users.
Now when I hit http://www.ipwireless.com/userguide in a new browser that is not authenticated, I'm able to access the page.
Just upgraded to 6.x-1.3 and flushed caches, but still no change.
Any ideas what I'm missing here?
John
Comments
#1
Any responses to this? I'm having the same issue. When I masquerade as an anonymous user and put in a direct URL to a page or blog entry that I've restricted to a specific role, I'm able to access the node. I have rebuilt permissions and flushed all caches. Using 6.x-1.3.
#2
Hi, I am also having the same issue.
I am using drupal for asset managment and I am using nodeaccess so just the attached customer and the admin staff can see the nodes but no one else can. I have everything unticked except the view box for customer node ref and admin staff. An anonymous user can still see the page.
Are there any stand out modules that get in the way of nodeaccess?
Thanks,
Paul.
#3
if you are using any other access control modules, that could be the problem. Beyond that, I'd need a database dump to see what's going on...
#4