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

[Bug 42764] New: codespell.t fails after container OS upgrade due to newer codespell dictionary
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '26

29 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42764 Bug ID: 42764 Summary: codespell.t fails after container OS upgrade due to newer codespell dictionary 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: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org When the KTD container OS is upgraded (e.g. Debian Bookworm -> Trixie), two things happen simultaneously that cause xt/author/codespell.t to fail: 1. The OS codename changes, so Koha::Devel::CI::IncrementalRuns finds no history in the ci-results repository for the new codename and falls back to a full scan of all tracked files. 2. The newer OS ships a newer codespell version (installed unversioned from apt in package-config.yaml). Each codespell release expands its misspelling dictionary, so words silently accepted by the old version are now flagged. The combination means the first full scan on a new container OS fails on pre-existing code that was never touched since the old codespell version accepted it. The .codespell-ignore file (currently 20 entries) was developed against older codespell versions and does not cover terms newly flagged by the upgraded version. Test plan: 1. Apply patch 2. Run xt/author/codespell.t inside the new KTD container => All tests pass -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 42592] New: Flag +count embeds that cannot be sorted
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '26

29 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42592 Bug ID: 42592 Summary: Flag +count embeds that cannot be sorted Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Depends on: 41950 After bug 41950, +count embeds backed by a DBIC relationship are automatically sortable. However, some +count embeds are only computed at the Perl level (no matching DBIC relationship) and cannot be sorted. Currently, consumers discover this only by receiving a 400 error when attempting to sort. We need a mechanism to flag or advertise which +count embeds are sortable and which are not. This could be: 1. An annotation in the OpenAPI spec (e.g. x-sortable: false on the embed enum value) 2. A response header listing sortable fields 3. Documentation in the API markdown 4. A dedicated endpoint or metadata response The goal is to let API consumers know upfront which +count columns support sorting, without trial and error. Discussion started in bug 41950 comment 17. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41950 [Bug 41950] Make +count embeds sortable by using SQL-level COUNT subqueries -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 41265] New: NoIssuesChargeGuarantees and NoIssuesChargeGuarantorsWithGuarantees circulation checks not precise enough
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '26

29 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41265 Bug ID: 41265 Summary: NoIssuesChargeGuarantees and NoIssuesChargeGuarantorsWithGuarantees circulation checks not precise enough Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Hello all When a checkout is performed, the NoIssuesChargeGuarantees and NoIssuesChargeGuarantorsWithGuarantees values are checked. This is an ‘if’ statement with check values, but by default, these are empty strings and therefore defined in this way. I therefore believe that the verification is not exactly what we want, particularly when SIP performs the checkout without permission to force it. Furthermore, in kohastructure, the default value would be NULL from what I understand, and it has not been included in the syprefs sql file. Perhaps there are some cases that I am overlooking, but I will suggest a simple fix anyway. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 41404] New: No need to check related guarantor/guarantee charges when the limits are not set
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '26

29 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41404 Bug ID: 41404 Summary: No need to check related guarantor/guarantee charges when the limits are not set 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In the code: # Check the debt of this patrons guarantees if ( defined $no_issues_charge_guarantees ) { # Check the debt of this patrons guarantors *and* the guarantees of those guarantors if ( defined $no_issues_charge_guarantors_with_guarantees ) { It is not possible to undef the system preferences, they are set as blank for no value - we need to check if they are numbers -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 42500] New: Update hold ratios (reserveratios.pl) to fetch data via API
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '26

29 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42500 Bug ID: 42500 Summary: Update hold ratios (reserveratios.pl) to fetch data via API Initiative type: --- Sponsorship --- status: 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com The Hold Ratios page is a pain point for larger systems with many holds. We should update how it fetches, displays, and interacts with data. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 52

[Bug 41489] New: Add "Create from Mana" to the Reports module home
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '26

29 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41489 Bug ID: 41489 Summary: Add "Create from Mana" to the Reports module home Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Mana-kb Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: alex.arnaud(a)biblibre.com We don't expose the module toolbar on the Reports module home page, instead opting to have the "New" options from it exposed in the 'main actions box' as "Create from SQL". If Mana is configured, we should add the option to "Import from Mana" or "Create from Mana" to this box. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 42239] New: Extended loan renewals
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '26

29 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42239 Bug ID: 42239 Summary: Extended loan renewals Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: performance Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: natasha.jones(a)westsussex.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Renewing an item with a specific date on the same date the item has been renewed (e.g. for holiday loan) does not work on Koha. This can be done the day after renewal though. For example, a customer renews their items online but sees the return date is when they are away. They contact the library on the same day to extend the loan further to a specific date. Koha doesn't allow staff to extend this renewal as it has already been renewed that day. It can be renewed from the following day though. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 40885] New: [OMNIBUS] Mana improvements to reports and subscriptions sharing
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '26

29 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40885 Bug ID: 40885 Summary: [OMNIBUS] Mana improvements to reports and subscriptions sharing Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Mana-kb Assignee: koha-bugs(a)lists.koha-community.org Reporter: elias.lorgnier(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: alex.arnaud(a)biblibre.com Created attachment 186975 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=186975&action=e… Yuno host app store as reference for a potential "create reports from mana" menu This OMNIBUS is made during my internship, it should allow community members to follow the progress made on mana. For SQL reports, we want to change the interface of creation, to make it look more like a plugin marketplace/app store, which would allow for discovering popular reports and having information such as number of imports and description directly visible. The following improvements are included : — Filtering out only reports that work on the current Koha version — Filtering reports based on language For subscriptions, we want to introduce : — a deduplication feature, that should allow multiple subscription models to exist for the same subscriptions, but never to have two identical subscription models for the same subscription. — This feature should allow us to implement a batch export to mana of current subscription numbering models from the Koha saved subscriptions table. Some of these features would be more fitted in the Koha-Infrastructure Product, but I could only select one product, and I try to focus on making mana useful to Koha users, and not just making mana better. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 41768] New: OPAC pickup location selector doesn't reflect available pickup location if you select a specific item
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '26

29 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41768 Bug ID: 41768 Summary: OPAC pickup location selector doesn't reflect available pickup location if you select a specific item Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org As of now, if I go on the OPAC to place a hold, I'm presented a list of available pickup locations for that biblio. However, If I click on "more options" and select a specific item with limited transfers, I can still select any pickup location available for the biblio. This leads to a user being able to select a pickup location and be denied the hold request only after confirmation, and then have to restart again (without knowing which libraries will work). I think that can lead to some frustration for users. This is quite similar to BZ33302 or BZ10993 but I will provide a new patch with the use of Koha's api and make the OPAC more similar to the intranet interface. -- You are receiving this mail because: You are watching all bug changes.

1 58

[Bug 39865] New: Consider updating OpenLibrary covers search API
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '26

29 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39865 Bug ID: 39865 Summary: Consider updating OpenLibrary covers search API Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oliver.behnke(a)aei.mpg.de QA Contact: testopia(a)bugs.koha-community.org Koha currently uses OpenLibrary's "Legacy Book API" [1] to fetch book covers which "is a legacy endpoint and may be phased out in the future". Also, it's inefficient. The replacement seems to be the dedicated "Covers API" [2]. One drawback, though, it's currently rate limited to 100 requests per IP per five minutes. That might quickly be exhausted on the OPAC search result page. Thanks [1] https://openlibrary.org/dev/docs/api/books [2] https://openlibrary.org/dev/docs/api/covers -- You are receiving this mail because: You are watching all bug changes.

1 1