Hello I have finally found the login UserControl but how come when I edit the control it doesn't seem to update on the site.

I started with basic changes like adding a "(TEST)" after the "Login" button text.  I thought the button would say "Login (TEST)" after I made the change but this was not so....

That file is in the ~/admin/Security/ folder

Possibly the DLL is already compiled???

Please help

KC

Try changing the language file - the idea of DotNetNuke and localisation is that it responds to your language settings.  So if you go to Host/Languages, edit the language .. then on the left hand side - look for the admin/security/ folder and click it - the languages that pertain to that login page will be visible on the right for you to change.

You don't change in the box and click update, you actually have to click a button that says - You're about to change the language* (words like that) and another editor will come up and enable you to change it.

Andother thing you can do, which is what I did is open the DesktopModules/Account Login  ascx file and change there - I think when I did that, it overrode the languages changes.

Then, what I did was put the account login button on a specific area on my site - - front page in fact, and then in the Admin/Settings/Advanced - changed the login page to be my front page.  BUT YOU MUST PUT THE LOGIN MODULE FIRST.. or it's fiddly to get back in.

Then I set the module for unauthenticated users, so it disappears when they are logged in.

A long winded story I know again, but this is how I've done it - so that on my home page, to make it all fit in nicely - I put the controls stacked one above each other, and then put Send Password to keep the words short and fit within the skin.

Nina Meiers

Yeah i'm an idiot lol.  I figurred out shortly there after that the login button text value in the signin.ascx.resx file was overriding the text="ButtonText" setting.  If i had just done a quick onClientClick='alert("Hey it worked");' then I would have seen that editing that file works fine.  Thx for the help. 

On a side note do you know at which point the Security Role cookies are set or if they are set as cookies at all.  I have my application login "piggyback" on top of the DotNetNuke login nicely so that it appears if you are logging into DotNetNuke but in reality are signing into my Membership application.  I then grab the proper DNN login from the user file in my database and login programmatically to DNN.  All i need to know now is how to alter on the fly the security roles when the user logs in.

Worse case scenario is i could create a pseudo login for each possible combination of security roles that i may need but that would be a pain in the ass sort of.