im posting this in the hope it may start a discussion on the types of bugs im getting straight out of the box with the recent DNN versions. no module installs, one page, one user. Windows server 2012 R2 very standard configuration, one other site running.
i have a brand new site to build so first i tried DNN 9.2. installed the site, logged in as superuser and changed the setting to login with email rather than a specified username. logged out, couldnt log back in. some research and apparently this feature is "broken" in DNN 9.2. this bug is very severe, still no fix.
so i stepped back to DNN 9.1.1. i was able to change the setting to login with email as username, and login again with the superuser account successfully. i logged out and created a test user, and before it was authorised, i attempted a login. i got a page load exception, the URL in the browser was modified to note the exception but no popups. when i clicked login again, the login box displayed a message to the tune of, "an critical error occurred, check the event log". the login box did not pop back up automatically. you do not want unauthorised user login attempts to generate an ugly exception, telling them to check the event log. need a more user friendly message
below is the event log for when an unauthorised user tries to login - which, by the way, would be very common if they have to wait for authorization. they will attempt to login just to test.
UserAgent:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
Message:Object reference not set to an instance of an object.
InnerMessage:Object reference not set to an instance of an object.
at DotNetNuke.Modules.Admin.Authentication.DNN.Login.OnLoginClick(Object sender, EventArgs e) at System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Server Name: xxx-DEV2