I have same problem with this.

Clean install and using Dynamic Login v2.2 module with new page call Login.  Page Management in Site setting set loginn page, but it still go to default login page.  I think it something to do with DNN 5.0, any idea to work around it?

Hi. I just wanted to follow up on this thread. Hopefully this will be corrected in the 05.01 release, I agree that obviouslly 3rd partys such as this component need their own support/questions but in this situation the 'Login' page is not even redirecting to the 3rd party component (even if you wanted the standard DNN login module on a seperate page, so its not really related to the component itself).

-Chad

www.datasprings.com

I am seeing something similar. I created a custom login control that is skinnable so it doesn't look all nasty, added that to a new Login page, and set that page as the login page.  The skin I am using has the Login skin object and the problem is that the skin object is appending "ctl/Login" to the querystring, thus loading the default login control instead of my custom control.  So it is actually going to the correct login tab, just bypassing my control.  Restarted the app, cleared the cache, but it is still happening.

This seems like something new in 5.x because I don't recall it happenning on my 4.x sites.  If I can't figure it out I suppose I can just hack some javascript in my custom control to strip the "ctl/Login" out of the URL.