Dotnetnuke core Account Login module (TUTORIAL)
A typical login module is shown below. It allows users to login to the dotnetnuke website you have created.
If you login to the website as an admin account and under the admin menu choose site settings you will the screen below as part of the Advanced Settings. This is where you may elect to create your own Login Page.
If you do, you can add an Account Login module to the page as shown below :
This can then be used instead of the default dotnetnuke login page.
You can choose to make it harder for "bots" to use the website by forcing CAPTCHA input as a means of logging into the website. To set the captcha code for login first go into the User Accounts section in the admin menu as shown below :
Then under the pop up menu for User Accounts, choose User Settings as shown below :
As part of the User Settings page, you will see options for setting the use of CAPTCHA for login and the use of CAPTCHA for registration. In this case you would simply tick the top option.
The User Log in screen now shows the CAPTCHA code needed to enter the website. It is italic and whilst reasonably easy for humans to understand, computer bots do not know how to read the 6 characters needed for a successful login, therefore keeping the nasty bots out of the website.
TIP : If you have recently noticed that when using version 4.5.3, that you can see the login module when not logged into the website, but whenever you login to the website, the login modules disappear, than you are not going insane... it was a code change made for this module. To see them again, just click on the Design button to swap to Design Mode and you will see the modules again so you can edit/modify the modules again. (The Design module can be found in the top left corner of the screen... at the far right of the 5 Page Function buttons or as shown below)
TIP : If you do happen to create a new login page for users but forgot to add the Account Login module so that you can login to the website again (crud... and that was exactly what I was thinking when I did it), then all hope is not lost as John Mitchell from Snapsis came to the rescue. See here. This pretty much grants you access to your website again and many kudos go to John for getting my heart beating again!!