Un-document feature for multi-website deployment under Single Umbraco Installation.
I was deploying my first Clinic Web Application and I was planning to have Multi-Website Deployment under a Single Umbraco Installation, so that I can add future web applications under the same setup.
By chance, I found an undocument feature in Umbraco for Login.
Follow there steps to have one Master Login Page for your Multi-Website Deployment under Single Umbraco Installation:
1. Create a Login master page named "Login" in Back-Office (it will show as "Login.master"). Desing this Login Master Page so that it is common to all websites under this common Single Umbraco Installation.
2. Create the code-behind "Login.master.vb" in VS in same folder as "Login.master". You can use this code-behined to add more control. For example, you can change the Parent Master Page depending on the current Root Website.
3. Create a "Login" Document (Login.aspx page) using Back-Office, anywhere in the Content Tree, which is based on "Login" master page.
4. Used the same default <authentication...> settings in web.config.
Now, any time authentication is required, this "Login.aspx" page will be invoked, even if the page url/path is incorrect.
I confirmed the above is working as mentioend, under Umbraco 4.0 and 4.0.2.
Actually, this seems to be expected behaviour. Any template that you create is approachable with just the template name, so if you create a template called "Search", you could go to site.ext/search.aspx and get the search template. Not sure what the "currentPage" variable will say, but it's probably going to be the homepage.
Un-document feature for multi-website deployment under Single Umbraco Installation.
I was deploying my first Clinic Web Application and I was planning to have Multi-Website Deployment under a Single Umbraco Installation, so that I can add future web applications under the same setup.
By chance, I found an undocument feature in Umbraco for Login.
Follow there steps to have one Master Login Page for your Multi-Website Deployment under Single Umbraco Installation:
1. Create a Login master page named "Login" in Back-Office (it will show as "Login.master"). Desing this Login Master Page so that it is common to all websites under this common Single Umbraco Installation.
2. Create the code-behind "Login.master.vb" in VS in same folder as "Login.master". You can use this code-behined to add more control. For example, you can change the Parent Master Page depending on the current Root Website.
3. Create a "Login" Document (Login.aspx page) using Back-Office, anywhere in the Content Tree, which is based on "Login" master page.
4. Used the same default <authentication...> settings in web.config.
Now, any time authentication is required, this "Login.aspx" page will be invoked, even if the page url/path is incorrect.
I confirmed the above is working as mentioend, under Umbraco 4.0 and 4.0.2.
I am not sure if this is a good thing or not.
Tarek.
Actually, this seems to be expected behaviour. Any template that you create is approachable with just the template name, so if you create a template called "Search", you could go to site.ext/search.aspx and get the search template. Not sure what the "currentPage" variable will say, but it's probably going to be the homepage.
In short, I don't see any problem here.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.