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

[Bug 38270] New: Add MARCXML options to ElasticsearchMARCFormat
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '26

28 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38270 Bug ID: 38270 Summary: Add MARCXML options to ElasticsearchMARCFormat Change sponsored?: --- 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 As noted on bug 27365, Elasticsearch search results don't get fetched correctly if a MARCXML record cannot be serialized in the compact ISO MARC 2709 format. One reason it might not be able to be serialized is due to 1 MARC field containing more than 9999 bytes or a whole record containing more than 99999 bytes. The change to be provided here will store MARCXML instead of ISO MARC 2709. -- During development, it may be found that a compressed form of MARCXML is preferred to an uncompressed form to be more comparable with the currently stored ISO MARC. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 27365] New: Koha doesn't check marcxml field size is < 10000 and fails in various places
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '26

28 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27365 Bug ID: 27365 Summary: Koha doesn't check marcxml field size is < 10000 and fails in various places Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hi ISO standard >The core of the framework is a MARCXML schema that allows lossless round-trip >conversion of an ISO 2709 MARC 21 record and an XML-encoded MARC 21 record. Thus a field size is 9999 bytes max. But /usr/share/perl5/MARC/File/USMARC.pm doesn't care: my $direntry = sprintf( "%03s%04d%05d", $field->tag, $len, $dataend ); and if len >= 10000 it silently creates a bogus directory with a length of 13 rather then 12. These non-conformed marxml will fail in various places. Export, search results list with elasticsearch which store ISO 2709 record in index and use them as data source in results list. eg: Easy to trigger in french UNIMARC with 359 (sorry in french) https://www.transition-bibliographique.fr/wp-content/uploads/2019/02/B359-2… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 56

[Bug 40960] New: Notifying holds should not print notice if no messaging preference is notified
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '26

28 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40960 Bug ID: 40960 Summary: Notifying holds should not print notice if no messaging preference is notified Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In overdue_notice.pl, holds_reminder.pl, no paper notice is sent to patron if no checkbox is checked. This should be the same for notifying holds. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 38201] New: VueJS architecture rethink
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '26

26 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38201 Bug ID: 38201 Summary: VueJS architecture rethink Change sponsored?: --- 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: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 37301 The goal is to streamline and provide a standard to how a regular CRUD component is implemented, instead of having to implement everything every time a new CRUD is required. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37301 [Bug 37301] Further improve how we build Vue components -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 74

[Bug 40650] New: Identity providers lack support for extended patron attribute type mapping
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '26

26 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40650 Bug ID: 40650 Summary: Identity providers lack support for extended patron attribute type mapping Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: oliver.behnke(a)aei.mpg.de QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Hi, so far we've been using LDAP authentication and with extended attribute type mapping (on register and login/update) but we have to move to OIDC. Thankfully there's an identity provider (IdP) for that. Great! However, testing and code inspection indicate that extended patron attributes can't be used for IdP mapping. When I try that I get: > There was an error authenticating to external identity provider > No property <ATTRIBUTE> for Koha::Patron At first glance, the code seems to support that assessment. For instance, the "update_on_auth" feature [1] calls set() which isn't overridden in Koha::Patron so Koha::Object.set() is being called [2], which of course isn't aware of those patron-specific extended attributes, eventually triggering the error above. To me that omission is a regression as existing auth methods like LDAP do support mapping extended patron attributes. Without that we can't rely on using identity providers since we'd lose required functionality. Thanks [1] https://github.com/Koha-Community/Koha/blob/8d31c2e06733fbc0f599ea99fe46df5… [2] https://github.com/Koha-Community/Koha/blob/8d31c2e06733fbc0f599ea99fe46df5… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 40596] New: Migrate CAS and Shibboleth into the identity providers
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '26

26 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40596 Bug ID: 40596 Summary: Migrate CAS and Shibboleth into the identity providers Change sponsored?: --- 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 When we envisioned the bug 31378 implementation, it was designed to cover other protocols as well. I'm filing this report to work on this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 80

[Bug 39556] New: mana-test.koha-community.org not working
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '26

26 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39556 Bug ID: 39556 Summary: mana-test.koha-community.org not working Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All URL: https://mana-test.koha-community.org/ OS: All Status: NEW Severity: normal Priority: P5 - low Component: Mana-kb (server) Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org Blocks: 39464 Trying to enable Mana in ktd gives "Cannot detect mana server at https://mana-test.koha-community.org, please ask an administrator to check your configuration." Comparing what https://mana-kb.koha-community.org/ and https://mana-test.koha-community.org/ serve to a browser, it sure looks like the Mana server isn't running on mana-test. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39464 [Bug 39464] Z39.50 Search results not highlighting grey rows in yellow when previewing -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 36192] New: [OMNIBUS] CSRF Protection for Koha
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '26

26 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36192 Bug ID: 36192 Summary: [OMNIBUS] CSRF Protection for Koha Change sponsored?: --- Product: Koha Version: master 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 34478 will be pushed soon, this bug will be for tracking remaining work with dependencies etc, more info to follow -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 157

[Bug 37993] New: Having a single EDI EAN account produces a bad redirect
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '26

26 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37993 Bug ID: 37993 Summary: Having a single EDI EAN account produces a bad redirect 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In acqui/edi_ean.pl: if ( @eans == 1 ) { my $ean = $eans[0]->ean; print $query->redirect( "/cgi-bin/koha/acqui/basket.pl?basketno=$basketno&op=cud-ediorder&ean=$ean" ); } So if you only have the single 'Library EAN' account Koha redirects to: /cgi-bin/koha/acqui/basket.pl?basketno=$basketno&op=cud-ediorder&ean=$ean This causes an error "op 'cud-ediorder' must not start with cud-" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 59

[Bug 41387] New: Add option for 2 digit month to serial patterns
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '26

25 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41387 Bug ID: 41387 Summary: Add option for 2 digit month to serial patterns Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The manual says: Numbering formula: this is what is used to create the number for each issue. You can use placeholders for up to three variables {X}, {Y}, and {Z} (which can be defined below), as well as predetermined variables: {Day} will be replaced by the date (two digits) {Month} will be replaced by the month number (two digits) {Year} will be replaced by the year (four digits) {DayName} will be replaced by the name of the day of the week https://koha-community.org/manual/23.11/en/html/serials.html#adding-serial-… But we actually replace the month with a single digit, we should have an option for 2 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13