Hello,

We are working on an Umbraco website which uses the standard Umbraco membership provider. This allows our visitors to create accounts, login and manage a online profile. This works great and thats lovely, fine & dandy.

However, if we then password protect the Root Node, using the standard 'Public Access' option available on every tree node, it causes us some problems.

-

The problem is the users hits the root page, and has to login using a simple username/password. 

Login is successful and they can see the site. 

Then then go to the 'My Account' page. At this point, an error is thrown, as technically a member is logged in, but in reality, we need to allow the user to login/register at this point.

-

Has anyone had any experience with this in the past and solutions? It's not a problem for a 'production' site, however we use the simple username/password protection available under public access, so when a site is in development the client has to login to see progress (which generally makes them feel happy and safe).

At present for us this means that deploying a site using Umbraco membership, means breaking the functionality of 'Public Access' within the Umbraco tree, which sucks a bit.

Laurie x