By mlcc2000 on
I have one Page that I want users to login (no anon. access) before they can see the contents on this page. Any suggestions on modules or mods that I can use? Seems so simple but I'm not finding anything.
Using version 4.7.6 with no additional modules other than the ones with the distribution.
Thanks,
mlcc2000
Comments
Taxonomy Access Control?
We're running version 5.1; based on what I've read, version 4.7.6 can only have one access control module. Pick something robust enough to grow with your needs!
If you require login to a see a page--regardless of the contents--maybe the Views module would help? I'm not sure.
If you require login for particular nodes, maybe Taxonomy Access Control (TAC) would help? It will be overkill for your needs now, but we're brainstorming how to gate content in a couple different places...with a couple different audiences...so it seems like the right choice for us.
We'll create a taxonomy vocabulary list called "Site Permission" and have terms like "public", "[audience 1]", "[audience 2]", and so on. In your case, you could go with two terms: "public" and "private" (or just "private" and not require your nodes to have a term from this vocab list).
Then, we'll create a Role for users that should have access to the nodes with the "[audience 1]" term selected. In your case, the "authenticated user" Role might suffice.
The TAC interface can be confusing, and I won't get into our complex use of it. Because you're only concerned about the users' ability to VIEW the page, I think you would need to select the "anonymous user" Role and, in the Site Permission settings (which obviously correspond to your vocab list), switch the radio button at the intersection of "private" and "View" to [D] (for Deny).
Of course, you would have to tag the login-required nodes with the "private" term from the "Site Permission" taxonomy vocabulary list.
We're still brainstorming here--our use of TAC is largely dependent on how well it will play with the Organic Groups module (we're using OG for a completely different purpose). I'm curious to see what other solutions are suggested for you.
http://drupal.org/project/taxonomy_access
http://drupal.org/project/views
"Nothing easy is ever simple." -- Plucky Duck