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

[Bug 12620] Proxy Add-on for Koha z39.50/SRU servers
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12620 Adolfo Rodríguez Taboada <adolfo.rodriguez(a)xercode.es> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #165452|0 |1 is obsolete| | Attachment #165835|0 |1 is obsolete| | --- Comment #17 from Adolfo Rodríguez Taboada <adolfo.rodriguez(a)xercode.es> --- Created attachment 201633 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=201633&action=e… Bug 12620 - Rebased patch onto current main (2026-07-07) Rebased attachment 165835 onto current main. Changes needed for the rebase: - installer/data/mysql/mandatory/sysprefs.sql: updated to the new 2-column INSERT format (variable, value) used since the installer SQL was simplified; options/explanation/type metadata now lives in .pref files. - koha-tmpl/.../admin/z3950servers.tt: [% USE Koha %] was already present in current main (added by a later commit); only the proxy checkbox block was added. - Minor context adjustments in C4/Breeding.pm and admin/z3950servers.pl due to whitespace reformatting in the surrounding lines. There are not functional changes from the previous patch. Greetings, Adolfo. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 41768] New: OPAC pickup location selector doesn't reflect available pickup location if you select a specific item
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41768 Bug ID: 41768 Summary: OPAC pickup location selector doesn't reflect available pickup location if you select a specific item Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org As of now, if I go on the OPAC to place a hold, I'm presented a list of available pickup locations for that biblio. However, If I click on "more options" and select a specific item with limited transfers, I can still select any pickup location available for the biblio. This leads to a user being able to select a pickup location and be denied the hold request only after confirmation, and then have to restart again (without knowing which libraries will work). I think that can lead to some frustration for users. This is quite similar to BZ33302 or BZ10993 but I will provide a new patch with the use of Koha's api and make the OPAC more similar to the intranet interface. -- You are receiving this mail because: You are watching all bug changes.

1 52

[Bug 42875] New: Wrong failure message when adding an item to a bundle
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42875 Bug ID: 42875 Summary: Wrong failure message when adding an item to a bundle Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- If bc_1 is checked out and I try to add bc_2 I get: "Failure: Item 'bc_2' belongs to another bundle" The POST returns 409 {"error":"Bundle is checked out","error_code":"bundle_checked_out"} The JS code: - } else if (response.error_code === "bundle_checkout_out") { - $("#addResult").replaceWith('<div id="addResult" class="alert alert-danger">' + _("Failure: Bundle is currently checked out") + "</div>"); -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 33817] New: Composition or an item bundle can be changed
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33817 Bug ID: 33817 Summary: Composition or an item bundle can be changed Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Circulation Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 42936] New: Display cardnumber under item status if no name is given
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42936 Bug ID: 42936 Summary: Display cardnumber under item status if no name is given Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- To reproduce: - HidePatronName = Show - Remove "surname" from BorrowerMandatoryField - Add a patron without any name information, but with a cardnumber - Find an item and issue it to the patron without a name - Find the detail page for the record that the issued item belongs to In the "Status" column, it will say something like "Checked out to A patron from Centerville: due 07/04/2026". It should give the cardnumber as a patron identifier, and the cardnumber should have a link to the patron detail page. This might sound a bit far fetched, but we do have a library that wants to store no name information in Koha, and only use the cardnumber to identify patrons. And Koha does allow patrons with no name information, so we should do our best to display useful information in this situation. The library in question says Koha used to show the cardnumber before the upgrade to 25.05, but the code responsible for displaying the patron information has moved around a bit, so I have not been able to pin point when the regression occured. As far as I can tell, the problematic code is this, which is in js-patron-format.inc in 25.05.x and in patron-format.js in main: if (name.replace(" ", "").length == 0) { if (patron.library) { return _("A patron from %s").format(patron.library.name); } else { return _("A patron from another library"); } } It makes the library name or "another library" display if there are no spaces in "name", but the reason there is no spaces in "name" could be that there is no name information to display. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 43002] New: We should consider moving to Node.js v22 or newer
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43002 Bug ID: 43002 Summary: We should consider moving to Node.js v22 or newer Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jake.deery(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Node.js v20 is now EOL. We should contemplate making the move to Node.js v22 or (better) v24. See Bug 38426 for what we did last time. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 41954] New: Patron hold history table should show hyperhold/hold group information
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41954 Bug ID: 41954 Summary: Patron hold history table should show hyperhold/hold group information Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: andrew(a)bywatersolutions.com, gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com In the staff interface, patrons' Hold history tab/holdshistory.pl should have a column for the hold_group_id. This will allow staff to readily see if an individual hold was part of a hyperhold, which will be important for troubleshooting. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

[Bug 43006] New: 'Current holds' table in patron hold history tab is missing column for hold_group_id
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43006 Bug ID: 43006 Summary: 'Current holds' table in patron hold history tab is missing column for hold_group_id Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- Created attachment 201623 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=201623&action=e… 'Current holds' table in patron hold history showing shifted columns In the 'Current holds' table in patrons' Holds history tab, there needs to be a column added to properly display the hold_group_id data introduced with bug 41954. The hold_group_id is showing, but it's in the Author column, and then the author is in the Barcode column, and each subsequent column is shifted by one (see attached). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 42555] New: (Bug 25314 follow-up) Destroyed labels for customized facets
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42555 Bug ID: 42555 Summary: (Bug 25314 follow-up) Destroyed labels for customized facets Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 25314 After applying Bug 25314, customized facets generated from mappings.yaml are displayed with the technical type_id instead of the proper label. This could be fixed with a simple correction in koha-tmpl/opac-tmpl/bootstrap/en/includes/opac-facets.inc: @@ -81,7 +81,7 @@ [% CASE 'Languages' %] <a [% attrs | $raw %] id="facet-languages">Languages</a> [% CASE %] - <a [% attrs | $raw %] id="facet-[% facets_loo.type_link_value | html %]">[% facets_loo.type_id | html %]</a> + <a [% attrs | $raw %] id="facet-[% facets_loo.type_link_value | html %]">[% facets_loo.label | html %]</a> [% END %] <div class="facet-collapse collapse show" id="[% facets_loo.type_id | html %]_collapse"> <ul> Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25314 [Bug 25314] Make OPAC facets collapse -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 41668] New: Elasticsearch reset not setting facets correctly
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41668 Bug ID: 41668 Summary: Elasticsearch reset not setting facets correctly Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org When resetting the Elasticsearch settings using mappings.yaml, it appears that the "Facetable" setting isn't being updated correctly. For instance, the default mappings.yaml says "publisher" is facetable, but after resetting the Elasticsearch from file, it says it's not facetable. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18