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

[Bug 27190] New: Debug REST API tests
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27190 Bug ID: 27190 Summary: Debug REST API tests Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org It can be tricky to debug REST API tests. You can get a "received 500 when 200 expected", but you don't have the error. There is one manual way to do it: $t->put_ok($url)->status_is(200)->json_is($expected_json)->or( sub { warn $t->tx->res->to_string }); But could we provide a generic way to add a diag in case Test::Mojo fails? -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 39936] New: Configure blocks per action and per interface in restriction types
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39936 Bug ID: 39936 Summary: Configure blocks per action and per interface in restriction types Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 23681 We should make patron restriction types more configurable. Within each restriction type, one should be able to choose whether to allow or block any of a list of actions from any of a list of interfaces. Actions to allow or block: - checkout - renewal - hold - ILL request - purchase suggestion Interfaces to allow or block each action via: - intranet - koha OPAC - SIP - API Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23681 [Bug 23681] Make patron restrictions user definable -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 41368] New: Tools/ManageMarcImport_spec.ts is failing
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41368 Bug ID: 41368 Summary: Tools/ManageMarcImport_spec.ts is failing Initiative type: --- Sponsorship --- status: Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Continuous Integration Assignee: tomascohen(a)gmail.com Reporter: lucas(a)bywatersolutions.com To recreate: 1. cypress run --spec t/cypress/integration/Tools/ManageMarcImport_spec.ts 2. It fails -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 37815] New: Protected flag permissions should be honoured in the REST API
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37815 Bug ID: 37815 Summary: Protected flag permissions should be honoured in the REST API 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: jake.deery(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com (follow-up from bug 36085) We now restrict access to the protected flag in the GUI. This should also be replicated out to the REST API. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 42080] New: Invoice PDFs are forced downloads
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42080 Bug ID: 42080 Summary: Invoice PDFs are forced downloads Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org Our acquisitions technician preferred being able to view invoice PDFs directly in the browser, behavior which bug 41591 changed to prevent a SVG XSS attack. We would prefer if invoice-files.pl served files inline with a CSP header instead of forcing a download. Basically, replace -attachment => $file->{'file_name'} with 'Content-Security-Policy' => "default-src 'none'; script-src 'none';". Arguably, Koha could add an op=view here so we could use JS to change the current op=download links to op=view if other libraries do not want to view files inline. But my assumption is that what our staff want is popular; it's not just extra clicks to find the downloaded PDF but a context shift to a reader app outside the browser. A more involved solution would be using a condition to download SVGs but render other attachment types inline. I believe inferring mime type from file extension is fine in this context since a browser will not execute code in an SVG served with a PDF mimetype, so "malicious.svg.pdf" would not work. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 41254] New: The filter for item status in item tables should be improved
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41254 Bug ID: 41254 Summary: The filter for item status in item tables should be improved Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In the table of items under a record, the filter on status created by Bug 37334 does not meet all the needs of a library because it groups together many different scenarios (in processing, on order, etc.) under a single status, "Not for loan." It is not possible to use this filter to isolate items on order, which is a frequent use case. I don't know what would be the best way to improve this filter. Perhaps we could add the different specific statuses provided for each value of notforloan<>0, prefixing them with "Not for loan" so that they appear close together - Excluded from loan (being processed) - Excluded from loan (on order) - Excluded from loan (non loanable itemtype) etc. And keep the global "Not for loan" renamed as "Not for loan (all reasons)". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 47

[Bug 39128] New: When Modifying a record using a template in cataloguing there is no link back to the modified record
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39128 Bug ID: 39128 Summary: When Modifying a record using a template in cataloguing there is no link back to the modified record Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucy.vaux-harvey(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Steps to reproduce this: - From a catalogue record, go to Edit > Modify using a template - At the batch record modification page select a MARC modification template to apply - Click on Modify selected records - You are taken to the Job enqueued page - There is no way to link back to your modified record from this page For this function where only one record can be modified at a time, the user should be automatically returned to the normal view of the record (there will not usually be any need to see the background jobs pages) or from the Jobs enqueued page there should be a link back to the record. As it stands now you have to either run a new search, use the browser Back button or click through to the background jobs and then pick up the link to the record from there. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 23908] New: Require patrons to confirm their email address
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23908 Bug ID: 23908 Summary: Require patrons to confirm their email address Change 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: pasi.kallinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Koha should require patrons to confirm their email address (by sending a confirmation email to the address) when the email is changed. This would prevent typos. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 28357] New: E-mail Verification
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28357 Bug ID: 28357 Summary: E-mail Verification 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Dead e-mails are a pain to deal with. It would be great if e-mail notifications were verified, regardless of registering online or in person. If an e-mail address is entered by staff, Koha should have a flag to indicate if the address has been verified. When an account is saved or updated, it should check if an e-mail address has been entered. If so, if it has not been verified, it should send a verification e-mail to the address. When the patron receives it, they should have to click something or login to complete the verification. The address is marked in their account as verified. If the address is changed at all, they have to re-verify. Staff who receive notice that the e-mail has problems (dead, full, etc) should have a flag they can set on the account to mark the address as bad, and the reason why. The patron would then have to supply a new e-mail address and verify again. While the account is flagged with a bad e-mail, notifications to that address should be turned off. If they have another form of notification, Koha could send them a notification that the e-mail address they supplied is no longer working, and needs to be corrected. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 42219] New: Patron verification process
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42219 Bug ID: 42219 Summary: Patron verification process Initiative type: --- Sponsorship --- status: 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com It would be helpful to libraries that strive to have accurate information on file to have an option, when creating a new patron, to have the entered information pop up on a clean modal displaying the information for the patron to review (we turn our monitor around for the patron to review). It would be great if everything fit on a modal cleanly and easily readable. It would also be great if there was an option for patrons to check next to each entry (or specified entries) to confirm the information is correct. Maybe you want them to look over everything, but only need them to verify that their phone number and email are correct. So, what would be ideal is: * Global/Branch level preferences * Preference to turn patron review on * Preference to indicate what information should be reviewed * Preference to indicate what information should be confirmed with a checkbox * Preference to indicate that when the confirmed items with a checkbox are changed by staff and the record saved, a modal with just that information will come up for that patron to confirm again. If the checkbox items are not changed on later changes, no modal confirmation is required. When the patron review is turned on, and the patron account is created and saved, before the form is submitted, the modal will come up with the requested items for review. I hope that makes sense. I think this would be helpful in some workflows. I know it would be in ours. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2