The change was intentional. There was quite a bit of internal debate prior to 6.0's release over whether the Login and Register controls should popup. For the most part the popup controls were designed for administrators and/or editors, and for most regular users the only popups they see are Register and Login.

In 6.2 as we are emphasising the ability to use social authentication providers, we found that oAuth authentication providers were not compatible with the popups, so the decsion was made to switch off popups for those two controls.

It is possible to switch them back on again - but not through the UI. The modulecontrol table needs to be updated and the SupportsPopUps column set to true.

In addition the skin objects would need to be changed as currently they generate the url for no popups.

---

Charles Nurse Chief Architect Evoq Content Team Lead, DNN Corp. Want to contribute to the Platform project? - See here

MVP (ASP.NET) and ASPInsiders Member

I was able to re-enable the popup for the login skin object by doing the following

(as with all database and core changes, I recommend you backup everything before proceeding, even then, proceed at your own risk. The ASCX.CS change is a core change that will be lost when you upgrade to the next release of DNN (unless it is put back into that release)

In the database I ran the following script 

update modulecontrols

set SupportsPopUps=1 where ControlSrc = 'DesktopModules/Admin/Authentication/Login.ascx'

In the /admin/skins/login.ascx.cs file I uncommented the following

if (PortalSettings.EnablePopUps && PortalSettings.LoginTabId == Null.NullInteger)

{

loginLink.Attributes.Add("onclick", "return " + UrlUtils.PopUpUrl(loginLink.NavigateUrl, this, PortalSettings, true, false, 300, 650));

}

---

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions

My login button issue can be seen at http://test.firstmennonitechurch.org/.... It behaves the same for Chrome, Firefox and IE9 (all on Windows).

The skin is XHMTL (http://store.dotnetnuke.com/home/prod...).

Chris Hammond:

I looked in the the database and the stock 6.2 source code and it already has the values you are suggesting. So I don't understand your post at all.