Okay. I almost had my whole week ruined.

I am using a skin that doesn't handle logins very gracefully, so I figured I'd just create my own. So I did just that and named it "Login" -- which is where it started going bad. I worked on the site a few more hours and after looking at the login page I had made I decided that I really didn't need a custom login for now, so I deleted it. A few minutes later I logged out. About an hour ago I went to log back in. Click the login icon and nothing. Just back to the homepage. Again and again. What the heck is going on!?!

So the internet search began. I was able to find a small aspx app that when run from the root of a DNN site, should get the login back -- and it worked. Then I tried to figure out what happened.

Apparently, if you create a page named "Login" (a special, reserved page name perhaps?)  then DNN considers it the login page, without being told. Then if you decide to delete that page and then log out, the login page can't be found anymore... Not good...

After using the aspx app I was able to get logged in. I restored the Login page I deleted earlier from the recycle bin. Renamed it to something else (I used "member signin") THEN deleted it. Crossed my fingers and logged out. Clicked the login icon and viola! Back in business. I was able to access my clients DNN site once again. BTW -- did I mention it was my clients new site? That's a conversation I wouldn't want to have, "I hope you like your site the way it is, because we can't log back in to change it. I kinda deleted the login page. But it was an honest mistake -- who KNEW!" I guess I should have. I do now, that's for sure.

I've been building websites based on DNN for a couple of years now, and this is the first time I've even heard of this. Is this something that everyone knows but me?

Sorry for the rant, but I was amped up just a little!

Jim

Do an internet search for "opensesame.aspx" and you should find it pretty quickly.

You should make a backup of your DNN database before doing anything. Also, be sure that if you have made backup(s) in the past, do not copy over the previous version(s) with this new backup -- as, it appears, your current version of the DNN db already has some sort of problem.

Still, it's better to have something as a fallback...

It worked on my site but -- USE AT YOUR OWN RISK!

Good luck!