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

[Bug 40997] New: Javascript error prevents saving when an instance of an 'important field is deleted
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '26

22 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40997 Bug ID: 40997 Summary: Javascript error prevents saving when an instance of an 'important field is deleted Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When a record has multiple instances of a field marked as 'important' and a cataloger removes one or more of the instances, and one is left in place, saving the record fails with: Uncaught TypeError: can't access property "getElementsByTagName", elem is null AreFieldsNotOk http://localhost:8081/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… Check http://localhost:8081/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… onOption http://localhost:8081/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… <anonymous> http://localhost:8081/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… jQuery 2 To recreate: 1 - In Admin - MARC bibliographic frameworks edit the default framewwork and edit 650 tag and mark it as important 2 - Go to cataloging -> new from z39.50 3 - Find a record with mulltiple 650 fields 4 - Delete one of the fields 5 - Attempt to save the record - nothing happens 6 - Check the console log in the browser, see the error noted above -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 16544] New: Changes to circ rules should be logged.
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16544 Bug ID: 16544 Summary: Changes to circ rules should be logged. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com At present, changes to circulation rules are not logged. This means that there is no way to determine what circulation rules were in effect at a given time, which makes historical trouble-shooting impossible. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 34069] New: Add ability to restore a recently deleted borrower from deletedborrowers
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34069 Bug ID: 34069 Summary: Add ability to restore a recently deleted borrower from deletedborrowers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be awesome to have the ability to restore a deleted borrower from deletedborrowers. Of course, if the borrower you need has been purged from that table for whatever reason, it wouldn't work, but it feels like an essential missing feature since we keep the data for Reasons anyway. Liz -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 109

[Bug 39233] New: Non-patron guarantor info not dropped when patron category is updated
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39233 Bug ID: 39233 Summary: Non-patron guarantor info not dropped when patron category is updated Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When child patrons category is updated via update_patrons_category.pl patrons relationship with their guarantor is dropped from borrower_relationships table. But non-patron guarantees info is still kept in borrowers table. To reproduce: 1. Find child patron with non-patron guarantor or create one. 2. Update patrons age so that their category is updated when you run following: perl misc/cronjobs/update_patrons_category.pl --confirm --too_old --from K --to PT 3. Check patrons info from borrowers table. => Note that values in contactname, contactfirstname and relationship columns were not dropped. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 41698] New: Add maintenance script to revert found holds for items currently checked out
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41698 Bug ID: 41698 Summary: Add maintenance script to revert found holds for items currently checked out Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz For reasons unknown, it is possible to get into a situation where an item is both checked out to one patron and associated with a found hold for another patron. We should add a script to Koha to fix items in this situation by reverting the found holds. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 41844] New: Save button does not work in cataloging when the first important repeatable field is deleted
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41844 Bug ID: 41844 Summary: Save button does not work in cataloging when the first important repeatable field is deleted Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When a MARC subfield is marked as Important and Repeatable in the bibliographic framework, it becomes impossible to delete the first occurrence of that field in the cataloging editor. If the first occurrence is deleted, the Save button does not work and the record cannot be saved. To test: 1- Go to Administration -> MARC bibliographic framework and click View default framework 2- Search for tag 653 and click Edit subfields 3- Click on subfield $a 4- Select Important, Repeatable, In 'Managed in' select tab 6 and in 'Visibility' select: OPAC, Staff interface and Editor 5- Save the framework 6- Find or create a record using the default framework. 7- Add a value in 653$a, clone the field and add a value in the second occurrence then save the record. 8- Edit the record again 9- Delete the first 653 field. 10- Click Save ---> It's impossible to save the record -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 27364] New: Making previous patron cardnumbers searchable
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27364 Bug ID: 27364 Summary: Making previous patron cardnumbers searchable Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: fiona.borthwick(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 18626 introduced the logging of changes to patron cardnumbers which is great, but this still does not link together previous cardnumbers. Imagine this scenario: A library patron loses their library card. They are issued with a replacement. Old and new cardnumbers are recorded in the Modification log. The old card is found (doesn't matter who finds it) and brought to the library. A member of library staff scan the barcode - get no results. This means they are none the wiser as to who this card belonged to. Would it not be a good idea to allow previous cardnumbers to be searchable? Some libraries may record this information somewhere in the patron record, but a search by cardnumber would be extremely helpful. It would be useful if the cardnumber moved into a linked field automatically when a new cardnumber was entered. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 26461] New: Incorrect handling of hold levels in SIP2 code
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26461 Bug ID: 26461 Summary: Incorrect handling of hold levels in SIP2 code Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com This may need to be split into 2 bugs, but problems are related. The SIP2 specification lists two fields for holds requests: AB - item identifier AJ - title identifier 1 - When placing a hold via SIP we always place a title level hold but only use the 'item identifier' to determine the biblio 2 - When cancelling a hold we use the 'item identifier' to identify the item and will only cancel an item level hold We should allow the use of the 'title identifier' for placing holds, and we should place an item level hold if 'item identifier' is passed or title level if 'title identifier' is passed with no item identifier We should do the same for cancelling. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 39665] New: batch_extend_due_dates should allow to extend dates from a list of patrons and a list of items
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39665 Bug ID: 39665 Summary: batch_extend_due_dates should allow to extend dates from a list of patrons and a list of items Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It you want to extend due date for some patrons, or some items (identified by a report for example), you cannot do it currently. It would be a nice improvement. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 27286] New: Patron picture-upload.pl allows arbitrary file extension during upload
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27286 Bug ID: 27286 Summary: Patron picture-upload.pl allows arbitrary file extension during upload Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: saiful(a)semanticconsulting.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 114546 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=114546&action=e… Double extension or wrong extension in picture file upload The IT team has flagged two issues with the picture upload tool (Patron Images feature): 1. The tool allows upload of files with double extension. 2. The tool allows upload of files with arbitrary file extension. In essence, the tool does not validate the image file restriction that is mentioned in the top of upload input tag which is: "Only PNG, GIF, JPEG, XPM formats are supported." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16