Yesterday I was tinkering with my new install of mojoPortal.  I added a blog to the home page, after adding a couple other modules, making a few other changes, and having gotten the jquery-ui skin how I liked it thanks to some help in the skin forum.  I have no idea what I did wrong, but suddenly I kept getting the generic asp.net error page.  I went into web.config and switched customerrors off, and got in.  But with customerrors off, the site works fine.  It gives me no indication of what the error is.  Switching it back to RemoteOnly, instead of the generic asp.net error page, I now get GoDaddy's generic error page.

I'm no web developer, so when it comes to web development, I may as well be lost in a wet paper bag, but I figured at least turning customerrors off it would give me an error that I could look up, but no, the site works fine.  Should I leave it this way, or is there a problem with that?  But that doesn't solve the underlying problem.

But then after that, another problem cropped up.  The sign out link stopped working.  Just quit.  Click it and it brings me back to the home page still logged in.  =/

New web site, still in the tinkering mode, still has the site closed message up, so I deleted the database, created new, and reinstalled the mojoPortal.  You'd think that might help.  Nope.  The link problem is solved now, but if I set customerrors to RemoteOnly, I still get the GoDaddy generic error page.  Not the error page that it is told to redirect to, but GoDaddy's error page.

Should I worry about it?