I've found that in both Umbraco 7.5.8 and 7.5.9 the account I create during the manual installation process breaks when my login times out.
I've seen this both on local (laptop) and server installations of Umbraco.
Fortunately, I've created a couple of Admin-level accounts during that initial session so I can log back in again. I've also noticed that this initial account no longer shows up as a User in the back office. However, as I look at the dbo.umbracoUser table I can see it there and it's not locked out.
BUT...
I noticed the userLogin for that initial account shows my email address NOT the userName. If I edit that row to remove the email address (in my case @syr.edu) and leave my username I can then login.
Should this be entered into the Umbraco Issue tracker?
Unsure of if it's a bug, but here are some things to consider:
Other users are unable to see the original user that was created as part of the installation of Umbraco.
Umbraco forces you to enter an email address when you install Umbraco, which it then uses as the username. Unless you change that, the email address will remain as the username.
User account created during installation breaks
I've found that in both Umbraco 7.5.8 and 7.5.9 the account I create during the manual installation process breaks when my login times out.
I've seen this both on local (laptop) and server installations of Umbraco.
Fortunately, I've created a couple of Admin-level accounts during that initial session so I can log back in again. I've also noticed that this initial account no longer shows up as a User in the back office. However, as I look at the dbo.umbracoUser table I can see it there and it's not locked out.
BUT...
I noticed the userLogin for that initial account shows my email address NOT the userName. If I edit that row to remove the email address (in my case @syr.edu) and leave my username I can then login.
Should this be entered into the Umbraco Issue tracker?
Unsure of if it's a bug, but here are some things to consider:
Thanks for those clarifications Nicholas. :-)
is working on a reply...