Noticed also that this breaks the password confirmation as well!

---

"if the only tool you have is a hammer you tend to see every problem as a nail" http://www.carawaydesign.com

Workaround:

Do not set a page for registration. Allow DNN to load the reg form but turn pop-ups off.

In our case this only works because we have a login page that is the home page. Users arrive at this page when the hit the portal. When they hit "register" DNN loads the registration module on the current page.

This means we can skin the login page and know that the reg module won't appear on some other page.

I'm getting a bit sick of all this crap though. DNN seems to be surging ahead with loads of new of and in our case, unwanted features. The User Accounts module is hideous and seems to have ballooned out of control. If does several jobs when really there should be separate modules for each. It's a nightmare to skin and horrible to configure.

Settings keep getting moved about to the point where I seem to spend forever trying to find them.

Why can't DNN developers just spend some time fixing all these bugs and build a really solid release that we can use before leaping off into another major release? I keep reading about major bugs that have hung around for several major releases. It's not doing us developers any good and it's not doing DNN any good.

With all the time we've wasted trying to workaround DNN issues we could have built our own CMS three times over.

rant over.. feel slightly better

---

"if the only tool you have is a hammer you tend to see every problem as a nail" http://www.carawaydesign.com