yes but this is just the mini login skin object I checked the code and it calls it the same way as the standard skin object. This does work OK with the Standard skin but then once they get to the register page on an upgraded instance it says user profile unavailable as I said before so 1 thing fixed and another 1 occurs. I will have to contact the people who made mini login to let them know that the register link does not work any more. Anyway thanks for your help on this just need to fix this registration problem now so that people can actually sign up.

Thanks
Paul

Get 1 step closer everyday.
Installed 5.4.3 on a new instance and once installed, I went to admin/site settings and then changed the register page to not specified and it all works OK but this still does not help my previous sites that are upgraded with faults.

Please can some one let me know of a way round this I have checked the forum over the past few days with no luck.

Thanks
Paul

I have upgraded to 5.4.2 and am having pretty much the same problem. Clicking on the skin's "Register" link redirects to the home page. Clicking on the "Register" link from the Login page does the same thing. Even trying to manually go to the ~/register.aspx page redirects to the home page!

So far, the only way I can get to the Register page is to visit it by adding a querystring, such as, ~/default.aspx?ctl=register. The problem with this approach is that I cannot find a way to make any of the Register buttons work this way.

I tried the suggestion of setting the Registration Page to "<None Specified>" in the Site Settings, but that does not work either. As a test, I set the Registration Page (in the Site Settings) to a regular page on my site, just to see if the Register links would go to that page, and they did. However, once I set the Registration Page back to "<None Specified>", the Register links started redirecting to the home page again.

It seems like the "register.aspx" url is not being recognized by DNN. Any help with this would be greatly appreciated--before I get in big trouble!

This is not the first forum post I have come across that addresses this problem, and none of them have been commented on by any DNN people. Please, DotNetNuke folks, give us some kind of response on this...fast!

---