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

[Bug 42361] SQL Injection in reports/catalogue_out.pl via Filter parameter (error-based, triggered when Criteria matches /branchcode/)
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '26

13 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42361 --- Comment #27 from Sanjarbiy <sanjarbiy11(a)gmail.com> --- CVE-2026-6428 has been assigned and published for this issue via TuranSecurity (a CVE Numbering Authority). Public record: https://www.cve.org/CVERecord?id=CVE-2026-6428 . Thanks to David and Jonathan for the fix and review. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 27105] New: Add checkout notes from staff client
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '26

13 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27105 Bug ID: 27105 Summary: Add checkout notes from staff client Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com AllowCheckoutNotes allows patrons to add notes for a specific checkout from OPAC. It could be useful we could have the same feature on Staff client. Librarians could add some useful informations for checking (annotated or highlighted text before the checkout, book already damaged, needs a new label after the return, etc.). A good feature to have less litigation with patrons when checking books with some problems ! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 10198] Add the ability to import and export authorized values
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '26

13 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10198 Narcis Garcia <narcisgarcia(a)gilug.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|narcisgarcia(a)gilug.org | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 5388] Circulation of related/requiring items (like Book and CD sets)
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '26

13 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5388 Mathieu Saby <mathsabypro(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mathsabypro(a)gmail.com --- Comment #3 from Mathieu Saby <mathsabypro(a)gmail.com> --- A colleague recently asked me how to handle easily the reservation of a book that comes with a CD, both of which are listed as separate items under the same record. I think that falls within the scope of this bug? I'm not sure bundles would be the best solution. I thought they were mainly for linking items from different records. In any case, we're not going to go to the trouble of creating bundles by hand just to group all the CDs with their accompanying booklets. I don't really understand the concept, but could "holding records" be a possible (though difficult to implement) solution in the future ? https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20447 -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 42841] New: Blocked hold request doesn't tell you that the patron already has it on hold
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '26

13 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42841 Bug ID: 42841 Summary: Blocked hold request doesn't tell you that the patron already has it on hold Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Target Milestone: --- I watched a clerk and director go around and around with a hold request they were trying to place for a patron. Both items in the record were marked in red, and there was a message at the top of the hold request page that said there are no items available, but they were looking at the items, and there was nothing glaring as to why they couldn't place the hold. After several minutes, they realized that the patron already had a hold on the item. The message at the top of the screen needs to be much less vague and say that this patron already has a hold on it. It should not give a generic reason. It should be specific. That would be helpful in so many ways. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 41979] New: Use translation in database updates for authorised_values
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41979 Bug ID: 41979 Summary: Use translation in database updates for authorised_values Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com When new authorized values are added to the database through the database updates (for existing installations), they are inserted in English. This causes problems for non-English installations. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 41688] New: Refund modal and amount as NaN, rejected comma separator
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41688 Bug ID: 41688 Summary: Refund modal and amount as NaN, rejected comma separator Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Point of Sale Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk Hello @ll The problem here is on the refund modal, when retrieving the default value before being modified it is NaN because in some cases for decimal separators with comma, the recovery fails due to formatting a value already formatted in js. After a quick search I think it's a return of bug 31513 fix -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 42840] New: Update some patron account and POS pages to use grid layout for forms
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42840 Bug ID: 42840 Summary: Update some patron account and POS pages to use grid layout for forms Initiative type: --- Sponsorship Sponsored status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 39780 Target Milestone: --- This patch will update the following templates to use grid layout for the forms: - includes/transaction_types.inc - members/boraccount.tt - members/mancredit.tt - members/maninvoice.tt - members/paycollect.tt - pos/pay.tt - pos/register.tt Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39780 [Bug 39780] Update library groups form to use grid layout -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 30680] New: Behavior due to MARC Overlay Rules should be reflected in Diff view when staging MARC batches for import
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30680 Bug ID: 30680 Summary: Behavior due to MARC Overlay Rules should be reflected in Diff view when staging MARC batches for import Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 14957 To recreate: - create a rule on /marc-overlay-rules.pl to protect the 050 tag when staging for MARC import - export a record from your collection and remove the 050 outside of Koha - reimport that record, matching your incoming record to the one already in your collection - confirm the Diff view on manage-marc-import.pl says the 050 will be deleted - complete import, confirm the 050 was retained We should somehow denote when a field will not be impacted due to an overlay rule. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 [Bug 14957] Write protecting MARC fields based on source of import -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 38527] New: Add logging of reports (created, run, changed and deleted)
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38527 Bug ID: 38527 Summary: Add logging of reports (created, run, changed and deleted) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: inkeri.hakulinen+bugz(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org For GDPR reasons it would be good to have Koha to log the use of reports. I suggest that the log should include data about -who created which report and when and what the sql was -who run which report and when and what the sql was (the actual sql that was run, since sometimes you choose / fill in some parameters when you run the report) -who changed which report and when and how the sql was changed (before & after) -who deleted which report and when and what the sql was -probably also the updates to the report descriptions would be good to log? However, the results of the reports should not be saved into logs, of course. This addition would bring transparency about the use of the reports. That would be important for preventing misuse of customer data. Now Koha doesn't collect so detailed data, and it would be easy to collect customer data without a trace in the logs. This data would of course be helpful also in cases, when someone accidentally changes a report so that it doesn't work anymore. You could detect the old report from the logs. Also this would help solving crashes that happened due to running too heavy reports. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7