Bug 8753 will only accept the patron's username. However some libraries do not use the username for identifying patrons, only their library card number. The "Forgot your password" feature should allow patrons to enter either their username or their card number in the Log In box (in addition to their email address) in order to reset their password.
Created attachment 63855 [details] [review] Bug 18616 - The "Add forgot password link to OPAC" should allow patrons to use their library card number in addition to username Allow patrons to enter either their library card number or user name in the "Log in" box for password recovery. Most patrons at our library use their card number to log in and are unaware of what their userid is. However there are some who have set a customized userid and would prefer to use that. This patch would allow either to be entered for password recovery. To test: 1. Enable the password recovery feature. 2. In the OPAC, click on "Forgot you password?" link and enter a valid library card number. 3. The error message "No account found with the provided information" appears. 4. Apply the patch. 5. Repeat step 2. The recovery email is now sent.
Tested - patch works as advertised. Tiny issue: Comment on line 59 reads: # Find the borrower by his userid or email Can you change the comment to reflect the code change (and make it gender neutral)? Maybe something like: # Find patron by cardnumber, userid or email
Created attachment 63881 [details] [review] Updated comment in code to reflect the change (and make gender neutral).
Created attachment 63882 [details] [review] Bug 18616 - The "Add forgot password link to OPAC" should allow patrons to use their library card number in addition to username Allow patrons to enter either their library card number or user name in the "Log in" box for password recovery. Most patrons at our library use their card number to log in and are unaware of what their userid is. However there are some who have set a customized userid and would prefer to use that. This patch would allow either to be entered for password recovery. To test: 1. Enable the password recovery feature. 2. In the OPAC, click on "Forgot you password?" link and enter a valid library card number. 3. The error message "No account found with the provided information" appears. 4. Apply the patch. 5. Repeat step 2. The recovery email is now sent. Followed test plan, works as expected. Signed-off-by: Marc Véron <veron@veron.ch>
Created attachment 63883 [details] [review] Updated comment in code to reflect the change (and make gender neutral). https://bugs.koha-community.org/show_bug.cgi?id=18616 Signed-off-by: Marc Véron <veron@veron.ch>
Hi David We have merge conflicts with Bug 16711: OPAC Password recovery: Handling if multiple accounts have the same mail address This patch is a one liner only, is it possible to redo it on top of 16711? Thanks! Marc
OK, I added the code to bug 16711. Should this bug be made obsolete?
(In reply to David Kuhn from comment #7) > OK, I added the code to bug 16711. Should this bug be made obsolete? Oh, I did not want to "steal" your patch :-) With "On top" I wanted to say: Make your patch dependent 16711. My original idea was the following: - First apply the patch from 16711 - Then do your changes for the library card number - Then attach your patch here (and obsolete the old ones) - Update "Depends on" and add 16711 - Obsolete the patch you added to 16711 Hmm, I could simply sign off your new patch and add it here... Lets see..
Created attachment 64066 [details] [review] Bug 18616 - The "Add forgot password link to OPAC" should allow patrons to use their library card number in addition to username Allow patrons to enter either their library card number or user name in the "Log in" box for password recovery. Most patrons at our library use their card number to log in and are unaware of what their userid is. However there are some who have set a customized userid and would prefer to use that. This patch would allow either to be entered for password recovery. To test: 1. Enable the password recovery feature. 2. In the OPAC, click on "Forgot you password?" link and enter a valid library card number. 3. The error message "No account found with the provided information" appears. 4. Apply the patch. 5. Repeat step 2. The recovery email is now sent. Note: Moved patch from 16711 back here and re-tested. Signed-off-by: Marc Véron <veron@veron.ch>
Thanks, Marc - I'm still kind of new at this. David
Created attachment 64608 [details] [review] Bug 18616 - The "Add forgot password link to OPAC" should allow patrons to use their library card number in addition to username Allow patrons to enter either their library card number or user name in the "Log in" box for password recovery. Most patrons at our library use their card number to log in and are unaware of what their userid is. However there are some who have set a customized userid and would prefer to use that. This patch would allow either to be entered for password recovery. To test: 1. Enable the password recovery feature. 2. In the OPAC, click on "Forgot you password?" link and enter a valid library card number. 3. The error message "No account found with the provided information" appears. 4. Apply the patch. 5. Repeat step 2. The recovery email is now sent. Note: Moved patch from 16711 back here and re-tested. Signed-off-by: Marc Véron <veron@veron.ch> Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
Pushed to master for 17.11, thanks to everybody involved!
Enhancement not pushed to 17.05.x
I feel like this would make this crucial feature much more useful as not all libraries are not using the userid, but the cardnumber as primary identification for the uses. Could be seen as an oversight of the initial implementation. Could you consider backporting this, Fridolin?
(In reply to Katrin Fischer from comment #14) > I feel like this would make this crucial feature much more useful as not all > libraries are not using the userid, but the cardnumber as primary > identification for the uses. Could be seen as an oversight of the initial > implementation. > > Could you consider backporting this, Fridolin? Yep since 16711 is in stable I will test this small patch
Fridolin, now that bug 18653 is resolved, would you reconsider?
(In reply to Katrin Fischer from comment #18) > Fridolin, now that bug 18653 is resolved, would you reconsider? Depends now on Bug 18956
(In reply to Fridolin SOMERS from comment #19) > (In reply to Katrin Fischer from comment #18) > > Fridolin, now that bug 18653 is resolved, would you reconsider? > > Depends now on Bug 18956 Bug 18956 is now pushed into stable releases... Now? ;)
Pushed to 17.05.x, will be in 17.05.06. No problem now ;)
This patch has been pushed to 16.11.x and will be in 16.11.14.
Pushed to 16.05.x, for 16.05.19 release