Create a new page, and then place the Login module on it.  On the Site Settings page, specify this new page as the Login page.

You can add other modules to this page.  You can add Text/HTML modules for instructions. You can add other modules.  You can skin this page to your liking.

If you want to style the Login module itself, you can use the following techniques:

• The LOGIN skin object has these attributes:   Text (The text of the login link), CssClass (The style of the login link, Default is OtherTabs), and LogoffText (The text for the logoff link)
• Use the Language Editor to change any of the text elements
• Use javascript to modify elements that have named IDs

I hope that give you some hints.

If you really want to supercharge the Login, I'd recommend that you look at Datasprings' Dynamic Login module.

Hi
I feel like a twit asking this but for the life of me I can’t locate the login module in my DNN 5 system. Would someone please point me in the right direction?
Regards
Richard

should be the first module in the list - (account login)

i had a problem last week where i restored my live site which uses ssl to my local pc and i could not log into the ssl login page

i managed to fix it by following a post archive post on dotnetnuke -

The only way to reset this is directly accessing the database. You have to set the LoginTab field on the Portals table back to the NULL value it had before.
Then restart the app so the change is noticed (editing the file web.config will do, just edit and save this file).

If you are using the default Login Module, it will be located at

http://yoursite.com/login.aspx

Hi
Thanks for the help but for some reason the login module is nowhere to be found. It's not in the module list, extensions or the module definitions and I can’t find it on the DNN site. Strange!
What we would like to do is extend the login and registration mechanisms. Where in the source code would we find these modules or their code?
Regards
Richard

You might want to look at Dynamic Login and Dynamic Registration from Data Springs rather than writing code.

Where the code lives, depends on the version of DotNetNuke.