In D5 I used LoginToboggan, some interesting block placement and page redirect to only allow anonymous users to the login page, the register page, and the register page. I may have also included an About Us node in their. Anyways it worked perfectly, I did not have to play with node access at all and it seemed completely secure. Back then I told people in the #drupal channel (which is now #drupal-contribute) and they started out by saying how that is not how its suppose to be done. After asking them why, they conceded that it was rather brilliant way to control access:)

Anyways, maybe amazing to include a walled garden section in your project. I wish I could pay for it, but all I have to pay with is time. I will pay it foreword (If I have not already), and continue to work hard on support and documentation, regardless of your decision.

Comments

steveparks’s picture

Status: Active » Closed (works as designed)

Hi MGParisi,

The aim is to keep LoginToboggan focused on a core feature set that applies to the broadest range of people, rather than add a range of different niche features. Please also see the maintainer's note about feature requests under the 'Maintainer's Commitment' section of the project page.

In your case it may be best to simply write a 'how to' for this use case, as it appears you managed to do it using existing modules in a clever way. You can add your howto here: http://drupal.org/documentation/customization/howto

I know there'd be plenty of people interested in your idea, so am sure it'd be a popular post.

Thanks
Steve