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

[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 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 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 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

[Bug 38514] New: Filter out autocomplete list of authorities with ConsiderHeadingUse
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38514 Bug ID: 38514 Summary: Filter out autocomplete list of authorities with ConsiderHeadingUse Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: roman.dolny(a)jezuici.pl QA Contact: testopia(a)bugs.koha-community.org After adding ConsiderHeadingUse system preference we can limit search results of authority finder plugin to authorities useable in specyfic type of fields (based on 008/14-16 data in authorities record). It would be nice to use the ConsiderHeadingUse system preference to filter out the autocomplete list of authorities when using authority finder plugin. To reproduce in standard KTD: 1. Apply Bug 38494. 2. Set ConsiderHeadingUse system preference to "Do". 3. Go to the Cataloging editor and open the authority finder plugin for the 650 field. 4. Type "Application" in "Search main heading ($a only)" field. 5. Notice two autocomplete values: "Application program interfaces (Computer software)" and "Application software". 6. Click search button. 7. There is only one result: "Application program interfaces (Computer software)". The expected behaviour is to filter out non-useable authorities from autocomplete list. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 41862] New: Encrypted database connection breaks with update to Debian 12
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41862 Bug ID: 41862 Summary: Encrypted database connection breaks with update to Debian 12 Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: cornelius.hertfelder(a)bsz-bw.de, markus.john(a)bsz-bw.de, tomascohen(a)gmail.com Depends on: 36026 We are currently using the encrypted database connectionas described in Bug 36026 with Koha 24.11.12 under Debian 11 with no issue When updating to Debian 12 the connection breaks with the error message: DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI connect('database=koha_instance;host=ourdbhost.de;port=3306;mysql_ssl=1;mysql_ssl_ca_file=/etc/ssl/certs/harica-ca.pem','koha_kohat',...) failed: SSL connection error: Enforcing SSL encryption is not supported at /usr/share/koha/lib/Koha/Database.pm line 75. at /usr/share/koha/lib/Koha/Database.pm line 123 Some additional information: - Database version: 11.8.3-MariaDB-deb12-log (on separate database server, unchanged by update) - DBD::mysql (4.004 ) 4.050 - DB connection can be established through koha-mysql and mysql/mariadb commands We’ve found a workaround editing Database.pm and adding the mysql_ssl_optional option: if ( $driver eq 'mysql' ) { $attr->{mysql_enable_utf8} = 1; + $attr->{mysql_ssl_optional} = 1; } At the same time enforcing encryption through the database user with: ALTER USER ... REQUIRE SSL; We assume that the problem is in DBD::mysql and is related to the way DBD::mysql (or Koha?) is enforcing SSL on the client side. As the workaround shows, DBD::mysql is still able to start a secure connection if it's not enforced that way. ** Related Debian bug report: https://bugs-devel.debian.org/cgi-bin/bugreport.cgi?bug=1032074 ** $ perl -MDBD::mysql -e 'print "DBD::mysql=", $DBD::mysql::VERSION, "\n"' DBD::mysql=4.050 $ dpkg -l | egrep 'libdbd-mysql-perl|libmariadb|libmysqlclient' ii libdbd-mysql-perl:amd64 4.050-5+b1 amd64 Perl5 database interface to the MariaDB/MySQL database ii libmariadb3:amd64 1:10.11.14-0+deb12u2 amd64 MariaDB database client library We changed nothing on the database server side during the upgrade of the Koha server from Debian 11 to Debian 12. The database server is on Debian 13 already and everything worked well with Koha 24.11 on Debian 11 but it stopped working with Debian 12. Documentation of DBD::mysql suggests this might not be the ideal solution: https://metacpan.org/pod/DBD::mysql 'Setting mysql_ssl_optional to true disables strict SSL enforcement and makes SSL connection optional. This option opens security hole for man-in-the-middle attacks. Default value is false which means that mysql_ssl set to true enforce SSL encryption. This option was introduced in 4.043 version of DBD::mysql. Due to The BACKRONYM and The Riddle vulnerabilities in libmysqlclient library, enforcement of SSL encryption was not possbile and therefore mysql_ssl_optional=1 was effectively set for all DBD::mysql versions prior to 4.043. Starting with 4.043, DBD::mysql with mysql_ssl=1 could refuse connection to MySQL server if underlaying libmysqlclient library is vulnerable. Option mysql_ssl_optional can be used to make SSL connection vulnerable.' Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36026 [Bug 36026] Add TLS MySQL connection without mutual authentication -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 42613] New: Javascript error on subscription-detail.pl if no orders (part deux)
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42613 Bug ID: 42613 Summary: Javascript error on subscription-detail.pl if no orders (part deux) Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org JavaScript error on subscription detail page when there are no orders. Same issue as bug 42611. Note though that it's NOT a problem in "main"/26.05 as table_dt is now defined using this invocation: let table_dt = table?.DataTable(); -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 34607] New: Add more option to sort lists
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34607 Bug ID: 34607 Summary: Add more option to sort lists Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: eugenegf(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 154725 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=154725&action=e… Koha list current sorting Currently, lists can only be sorted by the following: a) Title, b) Author, c) Copyrightdate, d) Call number and e) Date added. There is no option yet to sort it either by the following: a) A-Z, b) Z-A, c) (0-9 to A-Z), d) (Z-A to 9-0), e) newest to oldest, f) oldest to newest. Hopefully, this options can be added into Koha ILS. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7