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

[Bug 40809] New: JS warning should make Cypress tests fail
by bugzilla-daemon＠bugs.koha-community.org 27 Dec '25

27 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40809 Bug ID: 40809 Summary: JS warning should make Cypress tests fail Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 40434] New: Add maxLength to the vendor definition
by bugzilla-daemon＠bugs.koha-community.org 27 Dec '25

27 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40434 Bug ID: 40434 Summary: Add maxLength to the vendor definition Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 40175] New: Missing maxLength to REST API specs
by bugzilla-daemon＠bugs.koha-community.org 27 Dec '25

27 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40175 Bug ID: 40175 Summary: Missing maxLength to REST API specs Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com We do not specify the maxLength at the REST API specs level, even if the DB has one defined. Both must match. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 28702] New: Improve performance of C4/XSLT/buildKohaItemsNamespace
by bugzilla-daemon＠bugs.koha-community.org 27 Dec '25

27 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28702 Bug ID: 28702 Summary: Improve performance of C4/XSLT/buildKohaItemsNamespace Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This subroutine prepares items for XSLT parsing in search results, or opac lists. In bug 23414 it was refactored to use Koha::Items to reduce the number of lookups. In reviewing this code, it can be improved further - it is only called by XSLTParse4Display which is only called in 2 places: C4::Search->searchResults opac/opac-shelves.pl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47

[Bug 32702] New: Item statuses that block holds should be checked in CanItemBeReserved
by bugzilla-daemon＠bugs.koha-community.org 26 Dec '25

26 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32702 Bug ID: 32702 Summary: Item statuses that block holds should be checked in CanItemBeReserved Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests 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 Currently true holdability is a combination of CanItemBeReserved/CanBookBeReserved and IsAvailableForItemLevelRequest We should either combine these two routines, or ensure they are both called whenever needed. That is a long term goal, and this bug aims to simply move the item status checks to 'CanItemBeReserved' as they should reduce processing for any unavailable statuses to boost performance, and ultimately improve current functionality. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 55

[Bug 26537] New: Search does not work when no term in value_builder/unimarc_field_4XX.pl
by bugzilla-daemon＠bugs.koha-community.org 26 Dec '25

26 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26537 Bug ID: 26537 Summary: Search does not work when no term in value_builder/unimarc_field_4XX.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Cataloguing plugin value_builder/unimarc_field_4XX.pl has an itemtype filter. It does not work when used without a search term. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 55

[Bug 36518] New: Add unique IDs to the fieldsets of the item search form to facilitate customization
by bugzilla-daemon＠bugs.koha-community.org 26 Dec '25

26 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36518 Bug ID: 36518 Summary: Add unique IDs to the fieldsets of the item search form to facilitate customization Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be nice if we could add some IDs to the various section of the item form to make it easier to customize with CSS. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 25408] New: CanBookBeReserved should check "opacitemholds" policy
by bugzilla-daemon＠bugs.koha-community.org 26 Dec '25

26 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25408 Bug ID: 25408 Summary: CanBookBeReserved should check "opacitemholds" policy Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com how to reproduce : Set an issuing rule with opacitemholds set to "Force" Make a search and select multiple records Place a hold on those records (using multi-hold records) Verify hold is placed on the record (next item available) where it shouldn't! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 146

[Bug 36261] New: Calculating OpacHiddenItems is too slow in OPAC search
by bugzilla-daemon＠bugs.koha-community.org 25 Dec '25

25 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36261 Bug ID: 36261 Summary: Calculating OpacHiddenItems is too slow in OPAC search Change sponsored?: --- Product: Koha Version: master 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Calculating items and records hidden by OpacHiddenItems it slow. Too slow. Fortunately, I've come up with an optimization which seems to effectively eliminate the overhead added by OpacHiddenItems. Basically, instead of running 1 query per item, I run 1 query per bib to get all hidden items. It's pretty straightforward, but I'd like to battle-test it a bit more. I'm also writing this optimization for an older version of Koha, and I still have more optimizing I want to do, so I'm not going to post my patch just yet... It's coming though! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 41051] New: QueryFuzzy syspref description not clear about how it affects Elasticsearch.
by bugzilla-daemon＠bugs.koha-community.org 24 Dec '25

24 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41051 Bug ID: 41051 Summary: QueryFuzzy syspref description not clear about how it affects Elasticsearch. Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex(a)rcls.org QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)openfifth.co.uk, david(a)davidnind.com, philip.orr(a)lmscloud.de An otherwise intelligent sysadmin may wonder why Elasticsearch fuzzy searches with "~" don't work and go looking for answers. The current phrasing of the QueryFuzzy syspref is unclear and suggests that the syspref only affects users of Zebra. This is not the case, as the syspref must be set to "Try" on Elasticsearch systems as well in order to enable fuzzy searches. Current phrasing: [Try/Don't Try] to match similarly spelled words in a search. (For example, a search for flang would also match flange and fang; Currently only affects Zebra searches. Any Elasticsearch term can be made fuzzy by adding a ~ directly after the term.) Suggested wording: [Try/Don't Try] to match similarly spelled words in a search. (For example, a search for flang would also match flange and fang.) If using Zebra, searches become fuzzy by default. If using Elasticsearch, a term must be made fuzzy by adding a ~ directly after the term. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10