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

[Bug 41978] New: REST API auth/password/validation fails on patron with a null cardnumber
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41978 Bug ID: 41978 Summary: REST API auth/password/validation fails on patron with a null cardnumber Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: ovezina(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com If you create a patron without a card number (null) and try to validate their credentials using auth/password/validation, the request will fail. Error message : Expected string - got null. The failing point isn't the validation but the return values that Koha tries to send back in Auth/Password.pm. We simply need to send: cardnumber || "", for it to work again. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 41965] New: Mismatch between SMTP server and FROM branch in multi-branch notice sending
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41965 Bug ID: 41965 Summary: Mismatch between SMTP server and FROM branch in multi-branch notice sending 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: hammat.wele(a)inlibro.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 5

[Bug 32726] New: Authority search result display and relator terms in 22.05
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32726 Bug ID: 32726 Summary: Authority search result display and relator terms in 22.05 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: marius.mandrescu(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 15516] Allow to place a hold on first available item from a group of titles
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15516 Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |41983 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41983 [Bug 41983] Holds to Pull and Holds Queue should show when holds are part of a group -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39646] New: Send overdue notice to guarantor when guarantee has no email
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39646 Bug ID: 39646 Summary: Send overdue notice to guarantor when guarantee has no email Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: william.lavoie(a)inLibro.com QA Contact: testopia(a)bugs.koha-community.org If a guarantee does not have an email address registered to their account, then the script overdue_notices.pl doesn't send an email to their guarantors either. Additionally, if an email is sent, the letter should not be printed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 31484] New: Renewals disabled message doesn't display all reasons why something cannot be renewed
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31484 Bug ID: 31484 Summary: Renewals disabled message doesn't display all reasons why something cannot be renewed 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com There are many reasons why the renewals-disabled button might display in the issues table but not all of them will display depending on the circumstance, this can hamper librarians ability to make correct choices. For example: 1. Have an item checkout out what can be renewed at least one time BUT make that item overdue. 2. In the renewal column you'll see "0 Not allowed: overdue". That is good. 3. Have 'AllowRenewalOnHoldOverride' set to 'Don't allow' 4. Place the same item from 1-2 on hold. Make it an item level hold on that specific item. 5. Look at the issues table again, it still says "0 Not allowed: overdue". 6. The message should include some language saying the item can't be renewed becuase it is on hold AND it is overdue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 15834] New: Options to supress e-mail generated by AutoEmailOpacUser
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15834 Bug ID: 15834 Summary: Options to supress e-mail generated by AutoEmailOpacUser 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 Would love to see a selection when creating a new account to suppress the welcome e-mail generated by AutoEmailOpacUser. Sometimes, like when creating accounts for ILL, you don't want to send the info. It would also be great if there were a preference where you could choose patron groups to not send this e-mail to. Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 34994] New: Consider translations in updatedatabase
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34994 Bug ID: 34994 Summary: Consider translations in updatedatabase Change sponsored?: --- Product: Koha Version: unspecified 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: frederic(a)tamil.fr I wanted to open the discussion on this subject. Currently, when we insert things in the database using db_revs or updatedatabase, the strings are inserted in English. For a lot of things, like database structure changes and that type of stuff, it's fine. But for new letters, authorized values or additional content, it inserts in English no matter what the language of the installation is. That means that when we update Koha, we have to go in and translate all of those new things in the interface. We already translate the strings for new Koha installations through the translation of yaml files. I was wondering if it was somehow possible to use the yaml files and their translations to insert the new values? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 36737] New: Use translations in db_rev
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36737 Bug ID: 36737 Summary: Use translations in db_rev Change sponsored?: --- Product: Koha Version: unspecified 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 something is inserted in the db through a db_rev, it is inserted in English. For most things, it doesn't really matter. But in the case of authorized values and letters in particular, this is problematic in installations that are not in English. >From what I understand, people who have non-English installations correct these in an ad hoc fashion, sometimes through SQL UPDATE statements and other times manually in the interface. Since all the terms used in db_revs are also included in the installer yaml files, and those are translated, we should find a way to reuse the translations. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 38365] Add Content-Security-Policy HTTP header to HTML responses
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38365 --- Comment #236 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Jonathan Druart from comment #234) > (In reply to Jonathan Druart from comment #232) > > 3. Is there a good reason to use Plack::Test in > > t/db_dependent/Koha/Middleware/ContentSecurityPolicy.t? IMO we should have a > > Cypress test. > > Oh, it won't work with Cypress because you want to mock the config. Interesting. See also bug 41961. -- You are receiving this mail because: You are watching all bug changes.

1 0