DotNetNuke Login is not working!! How am I going to get back in?
This post is a follow up to a previous Can’t Login to your DotNetNuke Portal?
This is still happening to people every day, and the core team can’t agree on the best way to allow users to get back in. If you have inadvertantly set the LoginTabId setting to a different page but did not put a User Account SignIn module on that page, then you are probably wondering how you will get back in. After doing this some people usually realize that the “front door” to their website is locked and they don’t even have a keyhole right away because the login link stops working.
In that last post, I created a side door to display the login prompt, so that you could get back in to change the setting. And that was working great until some recent versions of the ClientAPI changed the way controls are loaded which blocked the “side door”.
The problem is easy enough to fix by changing the setting back directly in your DB, but some people don’t have that luxury, or simply would rather not mess around in the database.
So now I have created a “window” where you can slip your hand in and put the knob back on your front door.
Download this “Open Sesame” page and upload it to the root of your website, then execute by calling it in the browser (http://www.yourwebsite.com/OpenSesame.aspx) . All it does is update your DB for you to change the LoginTabId back to what it was. Which should get you back to your login prompt.
Big THANKS to John Mitchell
Posted on October 5, 2008, in Web Dev and tagged DotNetNuke Login is not working!! How am I going to get. Bookmark the permalink. 1 Comment.