When I set the Public Access of my site to the Home page, I get a server error. This server error does not occur if I set Public access to any othe rpage within my site... only the home page itself.
I can work aroud this, by setting my login page as the default site page... and then I can create a "onLoggedIn" handler script, whcih redirects. but this is far from ideal and I would like to use the inbuilt Public Access settings if I can because it works much better. e.g. in seeing the logged-in session, etc.
Is there a particular set up I need to use to set Public Access settings to my WHOLE site, including the Home page?
Whatever I tried, I was not able to set Public Access onto the site default page. So, I have created a new document type which contains a ContentPicker property. When I create this, I set it to be the site default page and set my 'Home' page as the content, so that it redirects.
This effectively prevents my site's 'Home' page from being the site default page and therefore allows me to place Public Access onto it without getting an error.
I still have no idea why I was getting the error but the work-around seems to work fine.
Public Access for site default page
I have seen this, previously posted:
http://our.umbraco.org/forum/core/general/15730-Limiting-Public-Access-to-pages-fails-with-server-error
And I have the same issue myself.
When I set the Public Access of my site to the Home page, I get a server error. This server error does not occur if I set Public access to any othe rpage within my site... only the home page itself.
I can work aroud this, by setting my login page as the default site page... and then I can create a "onLoggedIn" handler script, whcih redirects. but this is far from ideal and I would like to use the inbuilt Public Access settings if I can because it works much better. e.g. in seeing the logged-in session, etc.
Is there a particular set up I need to use to set Public Access settings to my WHOLE site, including the Home page?
Many thanks in advance.
Solution found. Well, a work-around at least.
Whatever I tried, I was not able to set Public Access onto the site default page. So, I have created a new document type which contains a ContentPicker property. When I create this, I set it to be the site default page and set my 'Home' page as the content, so that it redirects.
This effectively prevents my site's 'Home' page from being the site default page and therefore allows me to place Public Access onto it without getting an error.
I still have no idea why I was getting the error but the work-around seems to work fine.
is working on a reply...