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

[Bug 42540] New: Trap and throw elastic too_many_clauses errors instead of just dying
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '26

14 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42540 Bug ID: 42540 Summary: Trap and throw elastic too_many_clauses errors instead of just dying Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This started out as an issue with Connexion gateway, but it's not actually directly related. The issue is that during import, a record may contain so many fields to match on that it exceeds the max clauses an es server is configured for. In this case Koha 500's and connex emits the generic "Unsuccessful request" error. It seems the best patch forward would be to trap this error and propagate it as a Koha Exception, rather than simply die. There may be other elastic errors we could add to this pattern but I've not encountered any others so far. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 28846] New: MarcRecordFromNewSuggestion needs mapping to biblioitems.itemtype
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '26

13 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28846 Bug ID: 28846 Summary: MarcRecordFromNewSuggestion needs mapping to biblioitems.itemtype Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In C4::Suggestions, MarcRecordFromNewSuggestion uses mapping to biblioitems.itemtype : https://git.koha-community.org/Koha-community/Koha/src/commit/e9428f662fe2e… But this Koha to MARC mapping may not exists when itemtype is on item level. Same for biblio.autor, even if unlikely. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 42922] New: Require Authen::SASL >= 2.18
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '26

13 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42922 Bug ID: 42922 Summary: Require Authen::SASL >= 2.18 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Authen::SASL gets used by Email::Sender::Transport::SMTP, but from version 2.18 onwards it includes the module Authen::SASL::Perl::XOAUTH2 which allows Koha to use the XOAUTH2 SASL authentication mechanism with SMTP. Since Microsoft are moving towards XOAUTH2 authentication, it would be wise for us to backport this version for Koha. (It's available in Debian Forky which hasn't been released yet, and it's available in Ubuntu 26.04.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 38136] New: Refactor database translations (alternative)
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '26

13 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38136 Bug ID: 38136 Summary: Refactor database translations (alternative) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com This has the same goals of bug 24975 but with a different approach -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 85

[Bug 35200] New: Patron attributes should be translatable
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '26

13 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35200 Bug ID: 35200 Summary: Patron attributes should be translatable Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr I ran into this problem with a library that needed a lot of patron attributes, and they use self-registration. Their OPAC is in fr-CA, en, and es-ES. I created the patron attributes with labels in french. But then I had to write JQuery to translate them in en and es-ES. This is a sample of the js (I'm not a developer, so it might not be great, but it seems to work) $("html[lang='en'] body#opac-patron-registration a[name='patron-attr-start-1_NOM'] + li label").text("Baby's surname:"); $("html[lang='en'] body#opac-patron-registration a[name='patron-attr-start-2_DOSSIER'] + li label").text("Baby's file number:"); $("html[lang='es-ES'] body#opac-patron-registration a[name='patron-attr-start-1_NOM'] + li label").text("Apellido del bebe:"); $("html[lang='es-ES'] body#opac-patron-registration a[name='patron-attr-start-2_DOSSIER'] + li label").text("Número de expediente del bebé:"); I wonder if it would be possible to use the same process as translating the itemtypes (entry in localization table). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 39900] New: Add public REST endpoint for additional_contents
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '26

13 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39900 Bug ID: 39900 Summary: Add public REST endpoint for additional_contents Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: pedro.amorim(a)openfifth.co.uk Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: tomascohen(a)gmail.com CC: tomascohen(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 51

[Bug 42522] New: Holdings created in ERM with a linked bibliographic record do not show the link to the record
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '26

13 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42522 Bug ID: 42522 Summary: Holdings created in ERM with a linked bibliographic record do not show the link to the record Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com 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 -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 43206] New: cn_browser plugin red background on exact match is hard to read
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '26

13 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43206 Bug ID: 43206 Summary: cn_browser plugin red background on exact match is hard to read Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- In the cn_browser cataloging plugin we put a red background on items with a call number that exactly matches the search term. The black text on red background is hard to read and red implies that there's some sort of problem. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 43101] New: search_for_data_inconsistencies.pl creates a query that ORs every biblionumber in the catalog
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '26

13 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43101 Bug ID: 43101 Summary: search_for_data_inconsistencies.pl creates a query that ORs every biblionumber in the catalog Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Queries that use OR instead of IN are less efficient and can lead to situations where the query takes a very long time to complete due to row level scanning. We found one instance where they query had been running for over 10 days! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 43071] New: Test failures when Holds Allowed (daily) has a value
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '26

13 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43071 Bug ID: 43071 Summary: Test failures when Holds Allowed (daily) has a value Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- t/db_dependent/Holds.t, t/db_dependent/ILSDI_Services.t, and t/db_dependent/api/v1/holds.t all fail if the Holds Allowed (daily) circ rule has a value. They fail slightly differently for a non-zero value and for a zero. They pass if there is no value set for this rule. Non-zero: Test Summary Report ------------------- t/db_dependent/Holds.t (Wstat: 512 (exited 2) Tests: 74 Failed: 2) Failed tests: 64, 69 Non-zero exit status: 2 t/db_dependent/ILSDI_Services.t (Wstat: 256 (exited 1) Tests: 16 Failed: 1) Failed test: 6 Non-zero exit status: 1 t/db_dependent/api/v1/holds.t (Wstat: 2816 (exited 11) Tests: 12 Failed: 1) Failed test: 11 Non-zero exit status: 11 Parse errors: Bad plan. You planned 20 tests but ran 12. Zero: Test Summary Report ------------------- t/db_dependent/Holds.t (Wstat: 1024 (exited 4) Tests: 74 Failed: 4) Failed tests: 64-66, 69 Non-zero exit status: 4 t/db_dependent/ILSDI_Services.t (Wstat: 512 (exited 2) Tests: 8 Failed: 2) Failed tests: 6-7 Non-zero exit status: 2 Parse errors: Bad plan. You planned 16 tests but ran 8. t/db_dependent/api/v1/holds.t (Wstat: 2816 (exited 11) Tests: 12 Failed: 1) Failed test: 11 Non-zero exit status: 11 Parse errors: Bad plan. You planned 20 tests but ran 12 -- You are receiving this mail because: You are watching all bug changes.

1 17