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

[Bug 26288] New: Update the Select2 JS lib to version 4.1.0
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '26

11 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26288 Bug ID: 26288 Summary: Update the Select2 JS lib to version 4.1.0 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Bug 25727 updated Select2 to the latest stable release (4.0.13). We found some glitches about the width (see bug 25727 comment 19 for instance). It seems that the next 4.1 is going to fix it, but still beta. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 40879] New: Add system preference to enable/disable the “Cite” option in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '26

11 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40879 Bug ID: 40879 Summary: Add system preference to enable/disable the “Cite” option in the OPAC Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: Laura.escamilla(a)bywatersolutions.com Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The OPAC “Cite” option currently appears by default with no way to toggle it. Staff have requested a system preference that would allow libraries to enable or disable the display of the “Cite” link, or hide it entirely when not needed. This would give libraries greater control over OPAC features and better align with local citation practices. -- You are receiving this mail because: You are watching all bug changes.

1 101

[Bug 34482] New: Improve MARC21 7xx linking fields in bibliographic records [Omnibus]
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '26

11 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34482 Bug ID: 34482 Summary: Improve MARC21 7xx linking fields in bibliographic records [Omnibus] Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 52

[Bug 37061] New: Allow to define what information is automatically transferred from biblio to a new component record
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '26

11 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37061 Bug ID: 37061 Summary: Allow to define what information is automatically transferred from biblio to a new component record Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: piia.semenoff(a)ouka.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The cataloguing of the music material is in accordance with the RDA. It would be nice to be able to define which information is automatically transferred from the biblio to its component record (more specifically to 773 fields) when you create a new component record. It’s not possible to define through the staff interface what information is transferred from the biblio to the component record, because there is no system preference for these configurations. Fields are hard coded in Koha's source code. (C4\Biblio.pm, prepare_host_field). The information should transfer from biblio to the component record like this: 001 -> 773w 020$a -> 773z 022$a -> 773x 028$b 028$a -> 773o 245$a 245$b 245$n 245$p 245$c -> 773t 264$a 264$b 264$c -> 773d 300$a 300$e -> 773h In this bug by component record I mean e.g. a song of a note or a song of an album. I'm not quite sure what is the right term to use in this case. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 42425] New: Add checkin_id FK to accountlines to link fee adjustments to checkin events
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '26

11 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42425 Bug ID: 42425 Summary: Add checkin_id FK to accountlines to link fee adjustments to checkin events 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: 42418 Blocks: 24401 When AddReturn processes a checkin, it may create or modify several accountlines (lost item fee refunds/charges, processing fee refunds, etc.). Currently these fee adjustments have no persistent link back to the checkin event that triggered them. Bug 42418 introduced the checkins table as a first-class resource. Adding a checkin_id FK to accountlines would: - Allow Koha::Checkin->account_lines as a proper relationship - Enable embedding account_lines in the checkin REST API response (bug 24401) - Provide an audit trail linking financial transactions to the specific checkin that caused them - Eliminate the need to infer fee changes from timestamps or $messages parsing Implementation notes: - Add checkin_id INT(11) DEFAULT NULL to accountlines with FK to checkins.checkin_id ON DELETE SET NULL - Update AddReturn to pass the checkin_id when creating/modifying accountlines during return processing - The relevant C4::Circulation code paths are: _FixAccountForLostAndFound, _FixOverduesOnReturn, and the lost item fee charge logic Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24401 [Bug 24401] REST API: Check-in https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42418 [Bug 42418] Add Koha::Checkin(s) - checkin as a first-class resource -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 65

[Bug 33501] New: Cashup amount should be configurable
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '26

11 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33501 Bug ID: 33501 Summary: Cashup amount should be configurable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org It seems the Cashup summary only accounts for the cash payment type. We have a check payment type that should also be included. Am I missing a configuration somewhere, or do we need some way to define what should be included in the summary and intake balance? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 74

[Bug 31070] New: [DOCS] Did you mean? section needs an update
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '26

11 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31070 Bug ID: 31070 Summary: [DOCS] Did you mean? section needs an update Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org The Did you mean? section in the administration chapter needs an update (https://koha-community.org/manual/22.05/en/html/administration.html#did-you…) Updates required include: - Updated screenshots - Remove important note about it only working in the OPAC - Add information about the LibrisSpellCheck plugin Related changes to the searching preferences page: - Punctuation and spelling - Link to administration > did you mean section Other changes: - Check whether any update to the OPAC page is required -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 40445] New: Point of Sale reconciliation input during daily summaries
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '26

11 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40445 Bug ID: 40445 Summary: Point of Sale reconciliation input during daily summaries Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Point of Sale Assignee: koha-bugs(a)lists.koha-community.org Reporter: hdunne-howrie(a)westminster.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk We use a separate spreadsheet for our daily reconciliation of income taken which uses the cash register summaries. It occurs to me that this process can be streamlined by allowing an input stage to the summaries process so staff interaction with summaries is not the cashing up to package the transactions into a summary (we want the daily summaries to happen automatically) we want the staff input to be to add in (against totals for payment type and cash register) the amount of what was actually taken using the z reports and physical cash, i.e. a reconciliation stage so it will be easy for staff to see if the money is 'out' and then a process to reconciliate with a way to add in a note for the summary they are signing off with an perhaps a way for them to then 'balance the books' to account for the discrepancy. We would then need this staff input on the summaries (the physical amount taken and any notes) to be stored in a table, somewhere logical, so we can then report on this and create a way in which library managers can check in on this if needed and audit. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 352

[Bug 37473] New: Circulation rule holdallowed set to not_allowed results in warning when browsing a biblio record
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '26

11 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37473 Bug ID: 37473 Summary: Circulation rule holdallowed set to not_allowed results in warning when browsing a biblio record Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Circulation rule holdallowed set to not_allowed results in warning when browsing a biblio record : > No method count found for Koha::Items > DBIx::Class::SQLMaker::ClassicExtensions::puke(): Fatal: NULL-within-IN not > implemented: The upcoming SQL::Abstract::Classic 2.0 will emit the logically > correct SQL instead of raising this exception. at /home/koha/src/bin/../Koha/ > Objects.pm line 587 from C4/items.pm > 64 my @hold_not_allowed_itypes = Koha::CirculationRules->search( > 65 { > 66 rule_name => 'holdallowed', > 67 branchcode => undef, > 68 categorycode => undef, > 69 rule_value => 'not_allowed', > 70 } > 71 )->get_column('itemtype'); This results in pushing undef in an array and searching "not in" in that array, which is forbidden. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 29087] New: Holds to pull list can crash with a SQL::Abstract puke
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '26

11 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29087 Bug ID: 29087 Summary: Holds to pull list can crash with a SQL::Abstract puke 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: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Opening the holds to pull list page can crash with the following logged error: SQL::Abstract::puke(): [SQL::Abstract::__ANON__] Fatal: SQL::Abstract before v1.75 used to generate incorrect SQL when the -NOT IN operator was given an undef-containing list: !!!AUDIT YOUR CODE AND DATA!!! (the upcoming Data::Query-based version of SQL::Abstract will emit the logically correct SQL instead of raising this exception) at /usr/share/koha/lib/Koha/Objects.pm line 145 I've traced this to Koha::Holds->get_items_that_can_fill(). Among other things, this routine fetches a list of item types that cannot fill holds, i.e., cases where the 'holdallowed' rule value is 'not_allowed'. However, if your default rule is to not allow holds, the @hold_not_allowed_itypes list will end up including an entry whose value is undef. When passed to the item query, doing the -not_in filter on itype will result in the crash listed above. A quick fix might be to filter out undef from that list. That will fix the crash, but could lead to incorrect results if the default policy is to deny holds for all item types except for ones that are going to be specifically permitted. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 57