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

[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 20551] New: Add option for including deleted records in export_records.pl
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '26

07 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20551 Bug ID: 20551 Summary: Add option for including deleted records in export_records.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Add an option "--include_deleted" to also include possibly deleted biblios in export. This option can only be used together with --date, and --record-type=biblio. The rational behind this is that use case does not makes much sense (if you are doing a full export, why would you include deleted biblios) and thus some extra complexity can be avoided. Superficially related to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17693, not really quite different as this includes the whole biblio-record (with record status set to "d" in leader) in the regular export, not just biblio ids. This is a requirement for synchronizing with the discovery-system we are currently using for example and imho is a more standard and MARC-compliant way of supporting export of record deletions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 184

[Bug 40575] New: Transferring order will reload the page and its form
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40575 Bug ID: 40575 Summary: Transferring order will reload the page and its form Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Test plan: 1 - Create two baskets: "Source Basket" and "Dest Basket" 2 - Add one command line to "Source Basket" 3 - Close the basket 4 - Receive shipment 5 - Receive order 6 - Cancel the order receive 7 - Transfer the order to the Dest Basket -> When clicking on chose, you will be asked if you want to send again infos (which were sent to cancel the order receive), and if accepting, you will be printed an error. 8 - Apply patch 9 - Repeat the process with another source Basket and notice the page is simply reloaded without sending form. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 42386] New: Unify hold availability checks into Koha::Availability pattern
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42386 Bug ID: 42386 Summary: Unify hold availability checks into Koha::Availability pattern Initiative type: --- Sponsorship --- status: Product: Koha Version: Main 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 41728, 42385 Hold availability is currently split across three different interfaces with different return shapes: - Koha::Patron->can_place_holds â patron eligibility gate Returns Koha::Result::Boolean with messages - C4::Reserves::CanItemBeReserved â item-level hold policy Returns hashref with {status} - C4::Reserves::CanBookBeReserved â biblio-level hold policy Returns hashref with {status} This bug proposes unifying these into the Koha::Availability pattern introduced in bug 41728: - Koha::Patron::Hold::Availability â patron eligibility checks (expired, debt, restricted, card lost, global hold limit) - Koha::Item::Hold::Availability â item-level hold policy checks (hold policy, circ rules, on-shelf holds, pickup location, etc.) Both would return Koha::Availability::Result and support no_short_circuit and overrides, consistent with the checkin availability class. This would also require untangling patron-level checks that leaked into CanItemBeReserved (e.g. maxreserves in certain code paths) and pushing them back to the patron-level orchestrator. Note: This is a significant refactoring effort. CanItemBeReserved has ~15 different checks with complex interactions. A multi-patch approach is recommended. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41728 [Bug 41728] Add `Koha::Item::Checkin::Availability` to centralize logic https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42385 [Bug 42385] Extract _GetCircControlBranch into Koha::Policy::Circulation -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 64

[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 42169] New: Unify patron category change popups
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42169 Bug ID: 42169 Summary: Unify patron category change popups 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com On members/memberentry.pl if you change a patron category you will get 2 pop ups, one after the other. The first is a JS alert asking if you want to update patron messaging settings. The 2nd is a modal popup aking if you want to update the patron date expiry. This isn't very good UX. It would be nice if these could be unified into a single popup or at the very least, be similar types of popups. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[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