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

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

[Bug 41741] New: UpdateItemLostStatusWhenPaid should not apply to cancelled charges
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41741 Bug ID: 41741 Summary: UpdateItemLostStatusWhenPaid should not apply to cancelled charges Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If a library is using UpdateItemLostStatusWhenPaid to automatically update items' lost status when accepting payment, the status change also happens for charges that are cancelled from the Transactions tab of a patron's account. A separate system preference could be created for cancelled charges, but at a minimum, lost items whose charges are cancelled (not paid) shouldn't have their status automatically updated by UpdateItemLostStatusWhenPaid. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 37810] New: Some SUSHI providers return ServiceActive instead of Service_Active
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37810 Bug ID: 37810 Summary: Some SUSHI providers return ServiceActive instead of Service_Active Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 38782] New: BackgroundJobs/ErmSushiHarvester.t failing
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38782 Bug ID: 38782 Summary: BackgroundJobs/ErmSushiHarvester.t failing Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ERM Assignee: pedro.amorim(a)ptfs-europe.com Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 39075] New: Fix DB inconsistencies in the usage statistics module
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39075 Bug ID: 39075 Summary: Fix DB inconsistencies in the usage statistics module Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Highlighted here: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34587#c38 -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 41246] New: Deleting patron categories can leave orphaned rules in the overduerules table
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41246 Bug ID: 41246 Summary: Deleting patron categories can leave orphaned rules in the overduerules table 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com To recreate: 1. Add or have a patron category. 2. Go to Tools > Overdue notice/status triggers 3. Set some rules for that category. 4. Delete the patron category 5. Now do "select distinct categorycode from overduerules;" 6. The rule remains with a non-existent categorycode -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 41063] New: Additional fields are broken in Vue
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41063 Bug ID: 41063 Summary: Additional fields are broken in Vue Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: matt.blenkinsop(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, pedro.amorim(a)openfifth.co.uk To reproduce: 1) Go to Administration > Additional fields and add an additional field for erm_agreements 2) Enable ERM and navigate to ERM > Agreements 3) Click to add a new agreement and then fill out the form, making sure to add something into your new additional field 4) Hit save and navigate to the agreement you have just added 5) There will be no additional field added -- You are receiving this mail because: You are watching all bug changes.

1 27