SMF Version: SMF 1.1
After an easy upgrade from 1.0.8 to 1.1, our users could no longer store passwords in their browsers. Well, they could store them, but SMF continually tells us they're incorrect.
No problems logging on if one types in the username and password.
This is annoying. Anyone else experiencing this?
This is due to the change in how SMF handles password encryption. Some browsers saved the temporary encryption version. Internet Explorer apparently has problems while Firefox should work.
Edit: Removed useless link
Thanks. That's not going to make my users happy, though.
BTW, the link you provided brings me to an area for which I've no 'view' permissions.
Sorry.
Here is the post I was referring to.
Quote from: OrstioSaved passwords/autocomplete work in opposite ways between IE and FF. The different behaviour between the two browsers becomes very apparent when using the Mambo/Joomla bridge. IE inserts the saved value before form submission. FF saves whatever has been typed in before the javascript hash, but the autocomplete activates after form submission.
So, IE will save the last value before form submission, which is a blank. Yet it will still use what you type in the password field despite what is in the autocomplete value.
FF will save the correct value for the password as it was typed. But, the down-side is that if you ever change your password and have autocomplete turned on, FF may continue to input the old password, ignoring and overwriting whatever you type into the form.
The only way that both behave in any kind of similar fashion is if autocomplete is turned off, and javascript is enabled.
If you users choose to login forever that should make things a little less troublesome.
Thanks for the details. Appreciated.