website does not remember me
You must be logged in to post a reply. If you don't have an account, you can register.
|go123||I log in several times in a day and everytime i need to enter my nickname and password altough ''remember me'' button is clicked.
i do not know if this problem causes by my computer though. does it? or everyone is like me?
|harusaki||Well, seems the problem is on your computer because i don't have that problem.
Maybe, you should check whether you enable cookies on your browser
|beans||I have the same issue using Chrome on Ubuntu 14.04. There is no problem with the same feature on any other website.
Additionally, the site automatically fills in the login fields with "login or email" and a placeholder password so even though Chrome remembers my details for this site, I have to fill them in again anyway.
|marcel||Same here on Chrome 43 (latest version) on OS X 10.10 (latest version). Cookies are enabled. When I log in, I stay logged in, but when I log out, the name and password fields are blank, so the "remember me" function doesn't work for me.|
|marcel||I've looked at the page source and saw:
<input type="text" name="login" class="login" value="login or email"
onfocus="if(this.value=='login or email')this.value='';"
onblur="if(this.value=='')this.value='login or email';" /><br/>
<input type="password" name="password" class="login" value="password"
This way of displaying a placeholder is probably what interferes with the autofill. There is a more standard way, and that's the placeholder attribute:
<input type="text" name="login" class="login" placeholder="login or email" /><br/>
<input type="password" name="password" class="login" placeholder="password" / >
Could you try this please?
|marcel||Also, could you please enable newlines in forum posts?|
|claude||Yes, the newlines problem is a small one that has been around since quite a long time, we definitely need to fix this one. About the login problem, I don't think the problem comes from the placeholder, rather from the way the different browsers do handle login forms (the current implementation still has a known problem with firefox, but works with others). We'll review this, hopefully very soon. thanks a lot for your feedback.|
|nikwdhmos||I still have this issue on all my machines (Windows 7 and 8), running Chrome Version 51.0.2704.106 m|
This issue annoys me as well since it doesn't work in my laptop, tablet or phone browser (all Chrome by the way).
Looking at the code (and using a local proxy to tamper with the html) it seems the problem is caused by the fact that the actual field submitted has type hidden instead of password. Changing that to password causes Chrome to ask to save the password again and fill it in automatically.
The easiest and smallest fix would be to make the input type = password, put the second form in a 'display: none;' style and hash on the server. A proper fix would refactor the forms entirely.
Sorry for poking my nose in, but it would be so much easier if I could pick up my phone anytime I want and do a few problems, without needing to log in again. If I can help speed up fixing this a little I'll offer any help I can.
|Darrell Malick||Thanks Zteven. I agree, I hate having to log in all the time too. I'll get this to the top of the to-do list quite soon. Your analysis is helpful.|
|marcel||It really is annoying having to log in several times per day, even more so on a mobile device because of the more clumsy software keyboard.
Today it's the third time I've had to log in. Why is that? Sometimes the login is good for several days. Does it lose the sessions even when you're updating the website?
|Darrell Malick||Marcel: We did a bunch of software updates today, so I'm sure that prompted extra logins. Sorry about that.|
|xcombelle||It bothers me too.
Take the following suggestion with a grain of salt, I don't know the constraint of the software
A suggestion to really remember login despite the software update is to use a separate cookie for remember login than for session stuff. This new cookie as to be a one direction cookie -> id (a random string should be enough) and based on the cookie the user is deduced.
Post a reply