How to Configure DotNetNuke Websites to use DotNetNuke Advanced Login Module
DotNetNuke had the ability to configure a custom page to be used as the login page on your website. This page does not need to appear in your menu structure and the login process can effectively be made to use the Advanced Module in a seamless way to the default DNN login process.
Setup a Page for Login
1. Create a New Page in your DNN Website using the normal Add Page Method:
2. On that new page, uncheck the menu item for Show in Menu, and make the page viewable by all users or unauthenticated users:
This ensures that people who are not logged into your website have the permissions to view the login page.
3. Add the DNN Advanced Login Module to the web page, and format the page as desired. Remember too that you can have content that is visible in different states. i.e. Users that are not logged in can see modules and content set to “unauthenticated” but cannot see content for Authenticated users until they have logged in. We use this to our advantage on our DotNetNuke Module Download Page, by providing instructions to people about login before they are logged in, but after they are authenticated and logged in those instructions are no longer displayed.
4. Configure the module into the mode you wish to use for login. Options like logging in with email address in place of user name etc. This is an example we use for the login settings to our site:
5. To set the page you have just created as the default site login page, go to the Admin / Site Settings / Advanced Settings / Page Management, and select the page you have just created as the login page for the site, and set the Home Page as the page you wish to display by default after users have logged into your site:
The end result is that when someone clicks on the “Login” menu option in your DNN skin they will be directed to the login page of your website. Once authenticated the user will be directed to the Home Page, unless they were looking for a members only URL when they hit your website. In that case the login process will deliver the user to the original place they were attempting to reach.
I’m looking for a disclaimer page that needs to be accepted before the site can be viewed. Then a login page before protected pages can be viewed. Will this product do that?
Not alone, the disclaimer page could be done with our subscription module. And the signup and login with out Advanced Login Module for DotNetNuke.