February 2021 - Koha-bugs - lists.koha-community.org

[Bug 22881] New: Trying to clear search history via the navbar X doesn't clear any searches
by bugzilla-daemon＠bugs.koha-community.org 18 Apr '25

18 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22881 Bug ID: 22881 Summary: Trying to clear search history via the navbar X doesn't clear any searches Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: margaret(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- To Reproduce: 1) Run a few keyword searches on your Opac. You can be logged in or not, the behavior is the same. 2) Go to 'My Search History' the /cgi-bin/koha/opac-search-history.pl page. 3) Delete your past searches by selecting one or multiple searches and clicking the "Remove Selected Searches" button. You'll get an alert pop-up about what you are about to delete. The searches you selected should delete successfully. 4) Look at the little "x" (next to "Search History" in the Navbar). If you click on this "x" it will give you the exact same alert pop-up, however is you say yes, delete my searches, nothing will be deleted. Either the little "x" should not give you the option to delete searches nor the alert message or it should clear all your saved searches; as if you hit select all and Remove. Otherwise patrons who want to delete their history will be incorrectly lead to believe it was cleared if they don't check /cgi-bin/koha/opac-search-history.pl . -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 25996] New: Changes to debarments should be logged
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '25

16 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25996 Bug ID: 25996 Summary: Changes to debarments should be logged Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1 - verify borrower log is enabled 2 - click Edit on a patron 3 - on the edit page click "add a manual restriction" and enter a debarred comment, save the patron 4 - click Edit again, remove your restriction 5 - go to patron modification logs, see the log of your changes 6 - go back to the borrower checkout page, click to the Restrictions tab 7 - add a restriction 8 - delete the restiction 9 - go to patron modification logs, see there is not a log of your changes -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 46

[Bug 26170] New: Create "system" patrons that cannot be (easily) deleted via the web ui
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '25

16 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26170 Bug ID: 26170 Summary: Create "system" patrons that cannot be (easily) deleted via the web ui Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com At the moment, the only way to create OAuth2 or Basic Auth credentials is to generate a user. This user can be deleted by a librarian by accident, which will break your API integration with Koha. I propose that we make some system users that cannot be deleted from the Web UI. (Or users that can be deleted by a superlibrarian, but need to be "unlocked" first or maybe have their category changed, and a warning splashed that this will likely break integrations with other systems.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 78

[Bug 17815] New: Problems with search for dateaccessioned
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '25

14 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17815 Bug ID: 17815 Summary: Problems with search for dateaccessioned Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Tested this as described in bug 14861: Search from advanced search by accession date: 2011-09-01 - 2011-09-30 9461 results Searched with SQL: select distinct biblionumber from items where dateaccessioned between '2011-09-01' and '2011-09-30' 805 results The date range search doesn't seem to work right. The search for a single date appears to work correctly. It's also possible to truncate dates using *. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 26777] New: Give the user the option to display their patron card barcode from the OPAC
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '25

11 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26777 Bug ID: 26777 Summary: Give the user the option to display their patron card barcode from the OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org In this modern age, people are moving away from carrying cards.. but they nearly always have their smart phone to hand. It would be nice to be able to display your barcode for scanning at self service machines directly on your phone. -- You are receiving this mail because: You are watching all bug changes.

1 95

[Bug 23732] New: Hold rules checker: show matched rules and syspref values to help understand why a hold is possible or not
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '25

10 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23732 Bug ID: 23732 Summary: Hold rules checker: show matched rules and syspref values to help understand why a hold is possible or not Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 57

[Bug 27526] New: Remove Mod/AddItemFromMarc from additem.pl
by bugzilla-daemon＠bugs.koha-community.org 04 Apr '25

04 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27526 Bug ID: 27526 Summary: Remove Mod/AddItemFromMarc from additem.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org There is a lot of code in additem.pl that is transforming an item representation from/to HTML, XML, MARC::Record, Koha::Item We really don't need all this overhead, having the Koha::Item's attributes would be enough to update/create the item into the DB (it's no longer in the biblio MARC::Record!) Of course other places where we add/update items are valid as well: acquisition, batch item modification, etc. -- You are receiving this mail because: You are watching all bug changes.

1 203

[Bug 23780] New: Batch check out fails to inform or trap
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '25

03 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23780 Bug ID: 23780 Summary: Batch check out fails to inform or trap Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I have managed to catch failures in Batch check out on the following scenario: Patron has fines over the allowed limit. Item type only allows 5 check outs. When checking out 6 of this item type, Batch check out failed to: * Show any information that the patron had reached fine limit * Show that the patron was checking out too many of this item type If I checked out these 6 items without the fine, it gives the warning about too many items and asks me to confirm. If I check out 5 of these items with the fine, it does not explain why I need to confirm. It seems that Batch check out: * Is not displaying a reason for confirmation with the fine block. * Is not displaying a reason for confirmation when there are multiple blocks. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 16275] New: Prevent patron creation if the email already filled in borrowers.email
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '25

31 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16275 Bug ID: 16275 Summary: Prevent patron creation if the email already filled in borrowers.email Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nicolas.legrand(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some of our patrons are not sure they succeed their self registration and self register multiple times. We would like to prevent this by blocking the selfregistration if the field borrowers.email is already filled by the same email address. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 19366] New: PatronSelfRegistrationEmailMustBeUnique pref makes it impossible to submit updates via OPAC
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '25

31 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19366 Bug ID: 19366 Summary: PatronSelfRegistrationEmailMustBeUnique pref makes it impossible to submit updates via OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 16275 With PatronSelfRegistrationEmailMustBeUnique set to "Consider" I am unable to submit a change to my patron record via the OPAC because Koha performs the existing-email check on the email in the existing record I'm modifying. PatronSelfRegistrationEmailMustBeUnique should only apply new registrations. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16275 [Bug 16275] Prevent patron self registration if the email already filled in borrowers.email -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12