Closed (outdated)
Project:
Content Access
Version:
6.x-1.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Nov 2010 at 09:53 UTC
Updated:
24 May 2020 at 14:29 UTC
Jump to comment: Most recent
Comments
Comment #1
Esther Nelson commentedHi there,
I can see no-one has responded to you, but did you manage to find a solution yourself? I have the same problem, except I haven't even got around to creating any users or content yet - I've only just uploaded some contrib modules to my site and enabled them, and wham, the site cannot access any page at all. I've even deleted the content access module through my ftp program, but I'm still getting the same error message up! Looks like I might have to just delete the whole thing and start all over again.
Esther
Comment #2
torgospizzaI got this just now, when editing ACL / Content Access rules for only ONE node type. After a few minutes I decided to, for the heck of it, look at another node on the page - a DIFFERENT Node than the one I was adding access rules to - only to find that my test (non-Admin) user was denied access.
I had to rebuild permissions at /admin/content/node-settings/rebuild
This is a really bad bug. I don't know why editing one node type's permissions settings would affect all other nodes, even nodes of a different type. But if it requires me to have to rebuild permissions so users can still browser our site, that's fairly critical as far as bugs go.
I'll be digging into this more but would love any advice / ideas others may have.
Comment #3
good_man commentedAny useful reproduce steps? I can't reproduce it from your description?
Comment #4
good_man commentedComment #5
gisle