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

[Bug 42453] New: "About Koha" breaks if Elasticsearch is used but unavailable
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '26

14 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42453 Bug ID: 42453 Summary: "About Koha" breaks if Elasticsearch is used but unavailable Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org To reproduce in KTD: - Start KTD with ES: $ ktd --search-engine es8 up - Look at the "About Koha" page and verify it says ES is running - Stop the ES container: $ docker stop kohadev-es-1 - Reload "About Koha" and verify there is an error On KTD I get a stacktrace-type error page. On a live 25.05 install I get an error 500 page. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 42321] New: Breeding should handle empty results from SRU targets better
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '26

14 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42321 Bug ID: 42321 Summary: Breeding should handle empty results from SRU targets better Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently we see lots of warnings on e.g. the Folio LOC SRU server like: LOC SRU record 3: 61 LOC SRU record 4: 0 LOC SRU record 5: 0 LOC SRU record 6: 0 LOC SRU record 7: 0 LOC SRU record 8: 0 LOC SRU record 9: 0 LOC SRU record 10: 0 LOC SRU record 11: 0 LOC SRU record 12: 0 LOC SRU record 13: 0 LOC SRU record 14: 0 LOC SRU record 15: 0 LOC SRU record 16: 0 LOC SRU record 17: 0 LOC SRU record 18: 0 LOC SRU record 19: 0 LOC SRU record 20: 0 These are just empty results. (Note in a larger perspective, we probably should not search those SRU targets via the (old) ZOOM object.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 41889] New: Checkouts api call for checked in items can fail if the patron has been deleted
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '26

14 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41889 Bug ID: 41889 Summary: Checkouts api call for checked in items can fail if the patron has been deleted Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com To recreate: Checkout an item to a patron without anonymization and check it back in. Do a call to your instance (may need to turn on api basic auth and just use your credentials) that includes the date in question, see that you get a result. Delete the patron and send the call again, you'll get the error message at the bottom of the comment. This is a problem with third party report services. {ktdurl}/api/v1/checkouts?q={"checkout_date":{">": "2026-01-24T00:00:00Z","<": "2026-07-31T00:00:00Z"}}&checked_in=true&_per_page=5000&_page=1&_order_by=checkout_date Recreated on main, seeing it back at least to old stable. { "errors": [ { "message": "Expected integer - got null.", "path": "/body/0/patron_id" }, -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 41709] New: GIR segment data should be encoded in EDI ORDERs
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '26

14 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41709 Bug ID: 41709 Summary: GIR segment data should be encoded in EDI ORDERs Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org We're properly escaping special characters from bib/item records in EDI Order messages, but we don't apply that escaping to any of the GIR contents which may well also include special characters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 40610] New: Update OPAC templates to improve east of translation
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '26

14 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40610 Bug ID: 40610 Summary: Update OPAC templates to improve east of translation Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com Looking at [lang]-opac-bootstrap.po I see a lot of instances of repeated %s %s %s indicating opportunities to improve the markup structure to ease the translation process. This patch will tackle a batch of include files: koha-tmpl/intranet-tmpl/prog/en/includes/item-status.inc koha-tmpl/opac-tmpl/bootstrap/en/includes/biblio-title-head.inc koha-tmpl/opac-tmpl/bootstrap/en/includes/biblio-title.inc koha-tmpl/opac-tmpl/bootstrap/en/includes/date-format.inc koha-tmpl/opac-tmpl/bootstrap/en/includes/holds-table.inc koha-tmpl/opac-tmpl/bootstrap/en/includes/masthead.inc -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 34166] New: Show total price in table of suggestions
by bugzilla-daemon＠bugs.koha-community.org 14 Jul '26

14 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34166 Bug ID: 34166 Summary: Show total price in table of suggestions Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org For determining if a suggestion is accepted the price can play a big role. Sometimes libraries will have a separate custom status for items that need to wait for available funds. It would be great if Koha showed the total price of the suggestion in the table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 38621] New: [% today %] variable unavailable in report templates
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '26

13 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38621 Bug ID: 38621 Summary: [% today %] variable unavailable in report templates 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I tried adding a date to a report template, but it doesn't seem to work. I was told on MM that this is a bug. To recreate: 1. Create a report notice template with [% today %] 1.1. Go to Tools > Notices and slips 1.2. Click New notice > Reports 1.3. Enter a code and a name 1.4. Click Email 1.5. Enter a subject 1.6. In the message body, add some info with [% today %], here is what I used [% USE KohaDates %] [% today | $KohaDates %] [% FOREACH d IN data %] [% d.title %] [% END %] 1.7. Click Save 2. Create a report that works with this template 2.1. Go to Reports > Create from SQL 2.2. Enter a report name 2.3. In the SQL field, enter a report that would work with the template, this is what I used SELECT * from biblio limit 1 2.4. Click Save report 3. Click Run with template > Template name --> The date doesn't appear I also tried with a the simple [% today %] without the USE and without the KohaDates filter, but it doesn't show the date either. If I don't put the USE but use the filter, the template simply doesn't work (when you click Run with template > Template name, the report is displayed as normal in table form). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 40603] New: Add support for "uri" to OPACAuthorIdentifiersAndInformation
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '26

13 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40603 Bug ID: 40603 Summary: Add support for "uri" to OPACAuthorIdentifiersAndInformation Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org It could be nice to support 024$2 uri with the OPACAuthorIdentifiersAndInformation system preference, to display the information in OPAC and staff. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 42094] New: Tidy all script tags
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '26

13 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42094 Bug ID: 42094 Summary: Tidy all script tags Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 41324 On bug 41324 we tidy all the script tags that contained a kohaTable. Now we would like to tidy all the remaining script tags. We will certainly need a comment in the code to flag the script tag that is used to interpolate TT variables into JS variable. ``` <script> // Accept TT tags here let js_variable = [% perl_variable %]; </script> <script> // Here TT tags are prohibided, and ideally the code must be moved to a separate .js file // And we can reuse js_variable </script> ``` Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41324 [Bug 41324] Tidy kohaTable block -- You are receiving this mail because: You are watching all bug changes.

1 52

[Bug 42281] New: Tidy all script tags - authorities
by bugzilla-daemon＠bugs.koha-community.org 13 Jul '26

13 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42281 Bug ID: 42281 Summary: Tidy all script tags - authorities Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified 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: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 42094 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42094 [Bug 42094] Tidy all script tags (except value_builder) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 50