Summary: | Can not save new patron on fresh install (Conflict between autoMemberNum and BorrowerMandatoryField) | ||
---|---|---|---|
Product: | Koha | Reporter: | Marc Véron <veron> |
Component: | Patrons | Assignee: | Marc Véron <veron> |
Status: | CLOSED FIXED | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | fridolin.somers, gmcharlt, jlamb, jonathan.druart, krishna.moorthy94, kyle.m.hall, mik, mtj |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | String patch | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Bug Depends on: | |||
Bug Blocks: | 19225 | ||
Attachments: |
Bug 18636: Sysprefs: Add explanation for conflict autonumbernum / BorrowerMandatoryFields
Bug 18636: Sysprefs: Add explanation for conflict autonumbernum / BorrowerMandatoryFields Bug 18636: Sysprefs: Add explanation for conflict autonumbernum / BorrowerMandatoryFields |
Description
Marc Véron
2017-05-19 05:04:49 UTC
Hi, We are using Koha 17.05.01 with MySQL. When we try to add a patron, the card number field is not getting autogenerated and save is failing. Automembernum is enabled and BorrowerMandatoryField contains cardnumber. I see no contradiction in these parameters. This was working perfectly fine in 16.05. What could be going wrong ? Hi Krishna, this is more of a support question I think and would be better on the mailing list or in IRC. Please state which version of MySQL you are using. If it's 5.7 or later it's strongly recommended you switch to MariaDB as there are a lot of known problems with 5.7 being more strict. Created attachment 65699 [details] [review] Bug 18636: Sysprefs: Add explanation for conflict autonumbernum / BorrowerMandatoryFields This patch adds a note to the system preferences autonembernum and BorrowerMandatoryFields regarding a conflict if automembernum is on and BorrowerMandatoryFields contains cardnumber. To reproduce issue: See initial comment. To test: - Apply patch - Verify that in system preferences note appears with both prefs automembernum and BorrowerMandatoryFields Hi, The documentation as part of the patch says if AutoMemberNum is ON, then BorrowerMandatoryField should not contain cardnumber. If I remove cardnumber from the BorrowerMandatoryField, then on adding a patron a long number gets generated as the card number.This is happening after upgrading to 17.05. Earlier, we were using 16.05 and there the card number was getting auto generated by adding one to the last added patron's card number. So we had numbers like say 125, 126 etc(we are a small library) whereas the settings suggested in 17.05 leaves us with an unwieldy 14 digit card number. Katrin, I will reconfirm on the MySQL version. Am not sure about that. Do you think this is related to the autoincrement issue at the database level ? Hm, this might not be an update issue. The cardnumber is generated by looking for the biggest used number in your database and adding 1. If you do something like: select max(cardnumber) from borrowers; what does it give you? If you want to get back to low numbers, you might just have to clean up a few records. Created attachment 66516 [details] [review] Bug 18636: Sysprefs: Add explanation for conflict autonumbernum / BorrowerMandatoryFields This patch adds a note to the system preferences autonembernum and BorrowerMandatoryFields regarding a conflict if automembernum is on and BorrowerMandatoryFields contains cardnumber. To reproduce issue: See initial comment. To test: - Apply patch - Verify that in system preferences note appears with both prefs automembernum and BorrowerMandatoryFields Followed test plan, works as described Signed-off-by: Alex Buckley <alexbuckley@catalyst.net.nz> *** Bug 19224 has been marked as a duplicate of this bug. *** What about a warning on the about page? (In reply to Jonathan Druart from comment #8) > What about a warning on the about page? See Bug 19225 Created attachment 66730 [details] [review] Bug 18636: Sysprefs: Add explanation for conflict autonumbernum / BorrowerMandatoryFields This patch adds a note to the system preferences autonembernum and BorrowerMandatoryFields regarding a conflict if automembernum is on and BorrowerMandatoryFields contains cardnumber. To reproduce issue: See initial comment. To test: - Apply patch - Verify that in system preferences note appears with both prefs automembernum and BorrowerMandatoryFields Followed test plan, works as described Signed-off-by: Alex Buckley <alexbuckley@catalyst.net.nz> Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com> Pushed to master for 17.11, thanks to everybody involved! Pushed to 17.05.x, will be in 17.05.05. This patch has been pushed to 16.11.x and will be in 16.11.13. Pushed to 16.05.x, for 16.05.18 release |