I have the registration set to email verification. The registering member gets the email perfectly with the confirmation link. But when they click the link they get the rror message saying

"Permission Problem - Your usergroup does not have access rights to this module."

I do see their name as registered in admin but not activated. I also have the site set up as forced login before you can access the site. I believe THAT is the problem but I don't remember the fix, if there is one yet. But I do remember discussing this before here but for the life of me cannot find the thread.

Have you by chance configured your site to both have forced login and no read permissions for "members" module for Guests? 1.20 has addressed the issue with exceptions to forced login, but the latter would cause this. You can give Guests read permission for members module, they will only be able to see the validation pages in any case if you force login.

I have now changed the exceptions to apply in both cases in the 1.21 release, so if you can hang on for a couple of hours more you won't need to do anything about this, as I am now in the middle of fixing some final IE7 display issues, after which it's pack and upload time.

In 1.21, under core/variables.php, there's a new variable: $core['sys']['allowed_pages_override']. Under it, you can define all pages that will be displayed regardless of any restrictions you may have placed elsewhere.

Overall, I think the easiest way for you to have full control of your site access while allowing for a splash and other guest content pages is to allow the module "site" to have guest read permissions, and to limit read rights for guests in all other modules.

There is really nothing in the "Site" module that you couldn't do in other modules --- you can create custom pages with custom content under every module. It's there just so it's easier for you to separate your custom pages and your dynamic content. If you want to have two separate "pages only" areas, one private and one public, it's easy enough to clone the "site" module.

Read more on how to clone a module: iWiccle Module Reference / Adding new modules

"Have you by chance configured your site to both have forced login and no read permissions for "members" module for Guests?"

Yes, that's the way I've set it up. I figured the registering member wouldn't be considered a guest when they click that link in the email.

I can indeed wait a few hours for you to finish what you're doing... I'll go watch some Star Trek

Just updated the post above.

They are considered guests as they are not logged in... Giving them member-level access without login authentication can open up a number of possibilities for invading your site privacy.

A quick update before I crash for tonight -- just got admin access to a site (thanks AntiFmRadio) with the final IE7 battle raging on. In the meantime, I was slightly distracted with Keith and related research at a pub kept by our customers so I'll tackle this first thing tomorrow. (First pint of beer on a Friday night since god knows when!) In honor of that, the 1.21 release goes under codename Clurichaun. Keep up the spirits, good things are underway! (Go watch half a season of Star Trek TOS straight in the meantime, things ought to be ready by the time you're through the sacrament.)

If you want to have a complete builder-built splash page as your front page, and the rest of your site as "forced login", you could for example do this (aside the suggestion I gave earlier --- this is just for single pages rather than on a module-wide basis):

• Create a page called "splash" under your Site module
• Make that the default page of the Site module under Admin CP > Modules > Site
• Open /core/variables.php and add "splash" to the following at the beginning of the file:
  $core['sys']['allowed_pages_override'] = array('password_recovery', 'validate_account', 'splash');