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

[Bug 40936] New: Add index for default patron sort order
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40936 Bug ID: 40936 Summary: Add index for default patron sort order Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com The default sort order for Koha's patron search includes many columns, some of which are not indexed: [% CASE 'name-address' %] { "data":"me.surname:me.preferred_name:me.firstname:me.middle_name:me.othernames:me.street_number:me.address:me.address2:me.city:me.state:me.postal_code:me.country", Depending on the number of patrons in the database, and the specific configuration of the server, this can end up generating a query that creates a temp table in the hundreds of gigabytes of data or more. Not only does this risk crashing a database server with insufficient disk space, it's also incredibly slow. We've found a compound index prevents the issue and also makes the search much faster. InndoDB indexes have a fixed maximum length which is too small ( 3072 bytes ) to encompass the full data for all the fields we need to sort by. The following works well as a comprise to keep the index length within the maximum: CREATE INDEX idx_borrowers_sort_order ON borrowers ( surname(100), -- 400 preferred_name(80), -- 320 firstname(80), -- 320 middle_name(50), -- 200 othernames(50), -- 200 streetnumber(20), -- 80 address(100), -- 400 address2(75), -- 300 city(75), -- 300 state(40), -- 160 zipcode(20), -- 80 country(40) -- 160 ); -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 40679] New: Existing holds toolbar goes wonky if you select 'del' from priority dropdown
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40679 Bug ID: 40679 Summary: Existing holds toolbar goes wonky if you select 'del' from priority dropdown Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor 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 Created attachment 185598 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=185598&action=e… Example of wonky toolbar To recreate: 1. Have some holds 2. Go to reserve/request.pl?biblionumber=x for your biblionumber 3. Change at least one hold priority to 'del' 4. Notice the toolbar above the table with Update Hold, Cancel selected, Cancellation reason now looks wonky. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 40861] New: Weird hash key $ord->{'count(*)'} in serials/acqui-search-result.pl
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40861 Bug ID: 40861 Summary: Weird hash key $ord->{'count(*)'} in serials/acqui-search-result.pl Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org PLACK-INTRANET-ERROR.LOG PROD [2025/09/22 10:55:07] [WARN] Odd number of elements in anonymous hash at /usr/share/koha/serials/acqui-search-result.pl line 80. Associated code: push @{$loop_basket}, { basketno => $ord->{'basketno'}, total => $ord->{'count(*)'}, authorisedby => $ord->{'authorisedby'}, creationdate => output_pref( { str => $ord->{'creationdate'} } ), closedate => output_pref( { str => $ord->{'closedate'} } ), }; Note that SearchOrders does not create a key count(*) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 40759] New: Wrong date format in subscription brief history in OPAC
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40759 Bug ID: 40759 Summary: Wrong date format in subscription brief history in OPAC Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: normal 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 The brief history of a subscription shows the dates all in "database format" yyyy-mm-dd instead of using the formatting set in the DateFormat system preference. Dates on the subscription tab in the details page and full history are showing correctly. To test: * Add a subscription and receive 1-3 issues * Set the DateFormat system preference to format unlike yyyy-mm-dd * Go to the OPAC * Verify dates show corectly on the subscriptions tab itself * Click on more details * Verify dates how correctly in the full history * Verify the dates on the brief history are broken. /cgi-bin/koha/opac-serial-issues.pl? Example: Subscription information for ... The current subscription began on 2024-01-01 and is issued every month for 12 issues The first subscription was started on 2024-01-01 -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 38102] New: Checkout history in OPAC displaying more than 50 items
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38102 Bug ID: 38102 Summary: Checkout history in OPAC displaying more than 50 items Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In the Checkout history tab of the OPAC, the 'Showing last 50 items/how all items' feature isn't working properly in 24.05. If I have a patron with over 50 items, all items are displaying on that tab when 'Showing last 50 items' should be active by default. If I click 'Show all items' to reload the page (which shows, as expected, all items), but then click 'Show last 50 items', I still see all items, not just the first 50. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 39896] New: Syspref AuthorLinkSortBy is not working for Unimarc or custom XSLT
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39896 Bug ID: 39896 Summary: Syspref AuthorLinkSortBy is not working for Unimarc or custom XSLT Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The syspref AuthorLinkSortBy and AuthorLinkSortOrder depend on code in XSLT files. Currently, the code is only present in the default MARC21 files but it is not present in any UNIMARC files. Plus, if a library uses customs XSLT files (with syspref OPACXSLTDetailsDisplay, OPACXSLTResultsDisplay, XSLTDetailsDisplay, or XSLTResultsDisplay) they will not be able to use this functionality (unless they also updated their files but they have no way to know they need to do that). This is inevitable and is okay, but I think we should mention somewhere that these syspref depend on XSLT. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 40304] New: Zebrasrv config doesn't consider non-AMD64 CPUs
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40304 Bug ID: 40304 Summary: Zebrasrv config doesn't consider non-AMD64 CPUs Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: jake.deery(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Hi folks, As per this Mattermost conversation: https://chat.koha-community.org/koha-community/pl/ft6e47akutn6fbdg5tpwab5zbw I've identified an issue where running t/db_dependent/Search.t fails on AARCH64 machines. Upon investigation, I've found that in the default zebra-biblios-dom.cfg and zebra-authorities-dom.cfg files, the module search path does not include as many architectures as it should. I have rectified this, by copying the lines found in the debian/templates folder to the relevant config files mentioned in the last paragraph. Could I ask someone to check the patch I'm about to push, so we can get a quick conclusion to this bug? Ta, Jake -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 32950] New: marc modification template moving subfield can lose values for repeatable fields
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32950 Bug ID: 32950 Summary: marc modification template moving subfield can lose values for repeatable fields Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: bernard.scaife(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 146586 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=146586&action=e… mrc with multiple 020 fields including 020$z Moving one subfield to another fails for repeatable fields where the field to be moved doesn't exist in the first instance 1. Make marcmodtemplate as follows a. Move every 020 z field to field 020 a 2. Stage marc exchange file (attached) with following in 020 field (note only 7th and 8th have 020z and these are the ones we wish to move to subfield a) =020 \\$a9781003182870$q(ebk) =020 \\$a1003182879 =020 \\$a9781000407204$q(electronic bk. : EPUB) =020 \\$a1000407209$q(electronic bk. : EPUB) =020 \\$a9781000407167$q(electronic bk. : PDF) =020 \\$a1000407160$q(electronic bk. : PDF) =020 \\$z9781032023175$q(hbk.) =020 \\$z9780367760380$q(pbk.) 3. view staged record and observe fields 020 subfield a fields have all gone and subfield z has not been moved, but its value removed: 020 _a _q(ebk) 020 _a 020 _a _q(electronic bk. : EPUB) 020 _a _q(electronic bk. : EPUB) 020 _a _q(electronic bk. : PDF) 020 _a _q(electronic bk. : PDF) 020 _q(hbk.) _a 020 _q(pbk.) _a Note, adding a conditional to marcmodtemplate "only do this if 020 z subfield exists makes no difference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 39408] New: Cannot add patron via API if AutoEmailNewUser and WELCOME content blank
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39408 Bug ID: 39408 Summary: Cannot add patron via API if AutoEmailNewUser and WELCOME content blank Change sponsored?: --- 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries use Template Toolkit logic to avoid sending emails. In the case of the welcome notice they may only want to send for patrons fully added, not self registered. In the case of Aspen, we currently use the patrons API for self registration as there is not a self registration API. If you add logic like: [% USE Koha %] [% IF borrower.categorycode != 'SELFREG' %] Hello [% borrower.title %] [% borrower.firstname %] [% borrower.surname %]. Thank you for joining [% IF Koha.Preference('LibraryName') %][% Koha.Preference('LibraryName') %][% ELSE %]the library[% END %] You can search for all our materials in our <a href='[% Koha.Preference('OPACBaseURL') %]'>catalog</a>. Your library card number is [% borrower.cardnumber %] If you have any problems or questions regarding your account, please contact the library. [% END %] Then add a patron via the API in the self reg class: {"surname":"PATRON","firstname":"PROBLEM","library_id":"CPL","category_id":"SELFREG","email":"eample(a)example.org"} You get an error response: "Given does not exist" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 40985] New: Clarify POD of Holds->filter_by_found
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40985 Bug ID: 40985 Summary: Clarify POD of Holds->filter_by_found Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Most people read the following as contradictory: POD Returns a filtered resultset without holds that are considered I<found>. CODE return $self->search( { found => [ 'P', 'T', 'W' ] } ); -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12