I've recently realized that content I thought was for the eye's of only certain roles actually is not. Thank goodness the site's only in development!
I'm confused as to what else to do. I've made sure the ACL and related modules are up-to-date and aren't DEV versions.
I'm using the Content Access module & Forum Access modules. The Content Access doesn't work regardless of what I do. The Forum Access module prevents roles from seeing a forum, but if they have the URL of a post in a blocked forum they can gain access to that content.
Thinking it was an ACL issue, I tried the Node Privacy By Role module. But that doesn't work either.
I'm stumped and at a critical juncture that this is really bottlenecking the development process. Does anyone have any experience with this sort of issue?
Comments
Debugging necessary
I would guess that (a misconfiguration by you not in the game) it is some kind of interference between the different access control modules. They normally don't work well next to each other. So you might be best up to disable them all and after that enable one after another. After each module you put back in action you have to check if everything still works ok. Most likely you are going to notice some kind of interference after enabling additional access control modules.
Good suggestion. I didn't
Good suggestion. I didn't think to do that.
I've disabled all modules in the ACL section leaving only the Node Privacy by Role, which doesn't rely on the ACL. Then rebuilt permissions, rand update.php, cron; and cleared browser cache and Drupal cache. Still, everyone has access to content that should be restricted. This is the same with each privacy module one-by-one, as I activated one more and deactivated the previous one — so there was only one at a time operational.
It's a rather frustrating mystery. This really needs to get resolved, so I'm hopeful you'll have additional ideas. Thank you.
Something interesting I just
Something interesting I just noticed is if a create a View and limit access to the View within it's settings, that appears to work fine. This may be important troubleshooting information for those of you who are skilled in this sort of thing. I'm definitely not.
Solved
It turns out the problem was a conflict with the Domain Access module. After updating the module and installing an additional module, Domain Access Advanced, the problem was resolved.
Thanks for the Drupal communities help with this issue.