I have just created a new backend user and saved it. Then I figured that I forgot to give them access to the media section, so: edit, save... nothing happens.
As it turns out, I was getting an invisible error: Passwords must match.
Re-entering the password helped and I could save the user.
Password validation should be skipped when I haven't clicked "Change password", right?
I've experienced same issue, must be due to fact that browser prepopulates your password field with browser saved data (i mean, once you've instructed your browser to remember your password - both Firefox and Chrome offer this functionality), but only the first password box is filled.
It's probably because you have an add-on that automatically add your default password in one field (ie. a browser AutoFill). Anyone knows how we can disable that on an element?
Peter, click the link in my previous reply. However, to implement a fix, you'd have to change the Umbraco source, not really something I would recommend as your fix would probably break on the next upgrade.
I don't really understand why it would be so frustrating, how often do you change the user's information?
If it's really that bad, tell the clients to turn off autocomplete in their browser, if they don't want to give up autocompletion, they could use another, dedicated, browser to do Umbraco backend stuff and turn off the autocomplete in that browser.
Apologies for bumping an old thread but I've just re-read this and realised why this might have been confusing.
The bug occurs for our users in the MEMBERS section, not the Users section. Obviously this is a nightmare as it makes it impossible to save a Member without altering the member's password.
Save user bug
I think I've just ran into a bug:
I have just created a new backend user and saved it. Then I figured that I forgot to give them access to the media section, so: edit, save... nothing happens.
As it turns out, I was getting an invisible error: Passwords must match.
Re-entering the password helped and I could save the user.
Password validation should be skipped when I haven't clicked "Change password", right?
Sebastiaan,
I've experienced same issue, must be due to fact that browser prepopulates your password field with browser saved data (i mean, once you've instructed your browser to remember your password - both Firefox and Chrome offer this functionality), but only the first password box is filled.
Cheers,
/Dirk
Ah, that's good to know! Yes, I do indeed have password saving always on.
So in that case, it seems to me that if only one password field is filled in, it should still ignore validation.
Either that, or make the error visible when it's there, don't hide the error behind the "change password" field.
It's probably because you have an add-on that automatically add your default password in one field (ie. a browser AutoFill). Anyone knows how we can disable that on an element?
Ah yes, turning autocomplete off would be best. I have not researched how different browsers handle this but you can use autocomplete="off".
Can I also suggest that this property gets added to the ultimate picker's AutoSuggest feature, the autocomplete was annoying me there as well.
How does one go about adding autocomplete="off" to the User CMS control?
Happy to just be pointed at the doco for it - can't seem to find it myself.
Likewise the Members/Accounts section - this is proving very frustrating for our clients.
Peter, click the link in my previous reply. However, to implement a fix, you'd have to change the Umbraco source, not really something I would recommend as your fix would probably break on the next upgrade.
I don't really understand why it would be so frustrating, how often do you change the user's information?
If it's really that bad, tell the clients to turn off autocomplete in their browser, if they don't want to give up autocompletion, they could use another, dedicated, browser to do Umbraco backend stuff and turn off the autocomplete in that browser.
Apologies for bumping an old thread but I've just re-read this and realised why this might have been confusing.
The bug occurs for our users in the MEMBERS section, not the Users section. Obviously this is a nightmare as it makes it impossible to save a Member without altering the member's password.
Look like no-one solved this problem yet.
Here the solution:
Go to /umbraco/controls/passwordChanger.ascx
And add autocomplete="off" in both <asp:TextBox ID="umbPasswordChanger_passwordNew" and <asp:TextBox ID="umbPasswordChanger_passwordNewConfirm"
AutoCompleteType="none" don't work in most browser.
Cheers,
Shannon
is working on a reply...