If you are using our DotNetNuke Login Module the Advanced Login Module, or any other DNN login module, you may find that after you set the DNN Admin settings page to use a new page as the “Login” page.
You receive an error that looks like this:
A critical error has occurred.
This is caused by some behaviour in DotNetNuke that is programmed in for good reason, although it is a pain for us.
The idea is that you would not want to set your login page to a page that does not itself have a login module on it, otherwise you would potentially lock yourself out of your own site.
While this is not exactly true, because there are some little tricks to find a login page for DNN websites, the idea is noble, and it was for this reason that DNN corp. decided for a short time to make DotNetNuke check for the DotNetNuke Module on the page set as Login.
From DotNetNuke version 5.0.0 to 5.1.1 this was the case, then some people pointed out that this made it a pain to use DotNetNuke Login Modules from third party DNN module developers like InteractiveWebs.
Here is the thread: http://support.dotnetnuke.com/issue/ViewIssue.aspx?ID=10367&PROJID=2
So if you are faced with this error when using our module, the solution is easy. Upgrade your DotNetNuke website to a version later than DNN 05.01.01. In any case, the DNN 5 version was not really recommended until about DNN 5.2+ so upgrading is really a very good idea.