In Microsoft Edge editing a patron record takes away the password and you have to add it back in before you can save the record.
Our experience is somewhat different. When we edit any user record rather than the passwords vanishing they change from 4 asterisks and 4 asterisks (Password and Confirm Password) to 4 asterisks and 11 asterisks. Then the password length mismatch results in a standard error that the passwords do not match and the record cannot be edited without clearing both password fields. We are not actually using passwords, relying instead on LDAP, but we were planning to have library staff add a local password to their record so when our LDAP server fails then there is a fallback password, allowing staff to log in. This change will not work properly in Edge.
(In reply to Ray Delahunty from comment #1) > Our experience is somewhat different. When we edit any user record rather > than the passwords vanishing they change from 4 asterisks and 4 asterisks > (Password and Confirm Password) to 4 asterisks and 11 asterisks. Then the > password length mismatch results in a standard error that the passwords do > not match and the record cannot be edited without clearing both password > fields. We are not actually using passwords, relying instead on LDAP, but we > were planning to have library staff add a local password to their record so > when our LDAP server fails then there is a fallback password, allowing staff > to log in. This change will not work properly in Edge. This usually happens when the password for Koha was saved in the browser. Removing it, can help avoid the issue on the circulation desk. Emma, since this has been 2 years (and I can't test with Edge :( ), could you test if this is still an issue?
I've heard of related issues in Microsoft browsers but have never reproduced them. Curious to hear more...
I am unable to reproduce this problem. Because this report has gone so long without an update I'm going to consider it invalid.
(In reply to Owen Leonard from comment #4) > I am unable to reproduce this problem. Because this report has gone so long > without an update I'm going to consider it invalid. I feel like it's an issue with the browser as well. I'm not sure there is anything Koha could do even if we wanted to?
Hi all, Yes, this can be marked resolved, as we're not going down the Microsoft Edge route across our organisations so I've not tested this further. Many thanks.