Login will always be case-sensitive, as this is the standard across all login mechanisms for security reasons. If the owner sets username sUpEr8
, then the user shouldn't be able to login with super8
. Besides, when the backend checks input username vs stored username, they simply won't match if the cAsE is not identical.
You could change it by locating the following around line 405
:
trim($_POST['fusername']) == config::$username &&
Compare the two after lowercasing them instead:
strtolower(trim($_POST['fusername'])) == strtolower(config::$username) &&
hotgeart Because he clicked on the suggestion on his phone (Thomas) while taping.
He was speaking the login? I'm not quite sure why a browser would suggest an uppercase "T" on a password input field ... Browsers should normally never make suggestions on password input, unless the browser has already logged in once (and password was saved), in which case it should autofill the correct password.
😃 Have yourself a good day!