Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted October 13, 201113 yr I don't know if this is a bug or a new "feature". It just happened on this site this morning for the first time. Ever since IPS switched over to 3.2, the login field has read "email address", but has allowed logging in using my username. Today, however, it told me that was incorrect, and would not let me log in until I typed my email address there. Why the change?
October 13, 201113 yr You can configure whether you allow email or username logins in the ACP. We allow emails, primarily, because we utilize Converge.
October 13, 201113 yr I think this is a bug, I noticed the same change. But now I look into it, when you go to Log In Management. And change the settings of IPB Internal: Setting Login Method as Username, provides a login language string of Username or Email Not sure if it actually accepts both or if its just a language problem.
October 13, 201113 yr Author You can configure whether you allow email or username logins in the ACP. I know I can set it on my own board. I'm more asking what happened/changed here on community.invisionpower.com because I have always logged in with my username, and then suddenly today something changed and it forced me to use my email.
October 14, 201113 yr I don't know that we changed anything recently, but we've required email for quite some time. :unsure: Truthfully, however, very old members (such as myself) can still login with username. The problem we hit is that using Converge, the username is usually set to the email address, so people try to put their display name in (which isn't what is stored as their username behind the scenes) and can't login, which is why we only allow email.
October 14, 201113 yr I'm pretty sure I can login with my username. Which is different to my actual display name.
October 16, 201113 yr I can log in with both, and they changed / enabled email based logins a LONG time ago
Archived
This topic is now archived and is closed to further replies.