Well, we found the fix but only by trial and error!

But I can't help feel this can't be right..

<%@ Register TagPrefix="dnn" TagName="SIGNIN" Src="~/Admin/Skins/Login.ascx" %>
<%@ Register TagPrefix="dnn" TagName="LOGIN" Src="~/Admin/Skins/Login.ascx" %>

login and sign in now handled by exact same control?   Even though looking at host--> extenstions the signin points to a login.ascx under desktopmodules..

can anyone shed some light on this?

Gus

---

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

Well, to be sure I upghraded to very latest dnn 5.5.1 and then checked the situation.

There are two different user controls and they are called the same (login.ascx):

SIGNIN uses:

DesktopModules/Admin/Authentication/Login.ascx

LOGIN uses:

Admin/Skins/Login.ascx


But, the code for these controls is very different.  It seems to work now and does what is required. The signin is behaving as a signin and the login as a login.

We were utterly confused because the skin object docs that we found for <dnn:signin> pointed to:

Admin/Skins/signin.ascx

It would be really helpful if someone would explain why this is so and if/when it will be changed again. It's very confusing to us trying to work with it.

It reminds me of that "soft delete" balls up that went down a while back...  why release something in that kind of mess. It does nobody any kind of good
and causes us end users frustration and wated time. Wasted time means hours I can't bill for..

Gus

---

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