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

[Bug 42093] New: Use the REST API and kohaTable to list and search sysprefs
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42093 Bug ID: 42093 Summary: Use the REST API and kohaTable to list and search sysprefs Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 51

[Bug 35776] New: Wrong circulation rule displayed when parent itemtypes are used
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35776 Bug ID: 35776 Summary: Wrong circulation rule displayed when parent itemtypes are used Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com Follow the plans on bug 30324 - note the rule displayed is always the default rule. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 18139] New: 'Too many checked out' can confuse librarians
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18139 Bug ID: 18139 Summary: 'Too many checked out' can confuse librarians Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The too many checked out message can be very confusing for librarians when the limit specified is more or less than the number of checkouts the patron already has. We should make it clear to the librarian that this is only counting certain types of checkouts by giving them the issuing rule criteria used. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 54

[Bug 28639] New: Embed see-from headings (from authorities) into bibliographic records at OAI repository level
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28639 Bug ID: 28639 Summary: Embed see-from headings (from authorities) into bibliographic records at OAI repository level Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: julien.sicot(a)univ-rennes2.fr QA Contact: testopia(a)bugs.koha-community.org Hi, It could be interesting to enrich the bibliographic records exposed in OAI with see-from headings, this would allow users who use koha with a discovery tool to be able to manage, normalize and index some authorities data ? This is something that could be done directly in C4::Biblio::GetMarcBiblio following the same method used for embedding items. We could use an optional parameter like embed_items (embed_seefromheading) and a function similar to C4::Biblio::EmbedItemsInMarcBiblio by reusing what was made for zebra with EmbedSeeFromHeadings (bug #7417). Thanks for feedback, Best Julien Sicot Systems Librarian, Université Rennes 2 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 37202] New: Add a booking reminder notice to let patrons know they have an upcoming booking
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37202 Bug ID: 37202 Summary: Add a booking reminder notice to let patrons know they have an upcoming booking Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Blocks: 36666 Patrons may book items a long time in advance, they may need reminding that said booking exists and will need to be picked up. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36666 [Bug 36666] Bookings needs some slips and notices -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 40328] New: Issue with OpacMoreSearches HTML customization when depending on library
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40328 Bug ID: 40328 Summary: Issue with OpacMoreSearches HTML customization when depending on library Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Issue with OpacMoreSearches HTML customization when depending on library. It only works on main page. Looks like code is incorrect : [% SET OpacMoreSearches = AdditionalContents.get( location => "OpacMoreSearches", lang => lang, library => branchcode || default_branch ) %] Should use "library => logged_in_user.branchcode" -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 40949] New: Bookings to collect shouldn't tell staff to check in items
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40949 Bug ID: 40949 Summary: Bookings to collect shouldn't tell staff to check in items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aude.charillon(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Depends on: 33736 On the Bookings to collect page (pendingbookings.pl), under the headers is the text: "The following items have not been collected for bookings. Please retrieve them and check them in." The second sentence does not make sense: checking items is relevant for holds but bookings do not need to be checked in. The second sentence should be removed on this page - or updated to something relevant to bookings. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33736 [Bug 33736] Add bookings to collect circulation report -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 40808] New: Holds charges should be accessible from Holds
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '26

09 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40808 Bug ID: 40808 Summary: Holds charges should be accessible from Holds Change sponsored?: --- 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: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com It should be easy to get from a hold to it's associated charges.. i.e. Hold fee, Cancellation fee, any processing fees. This would be useful for API responses and display purposes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 41977] New: Hold fee not charged for title-level holds when all items have negative notforloan status
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '26

09 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41977 Bug ID: 41977 Summary: Hold fee not charged for title-level holds when all items have negative notforloan status 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: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com When a hold is placed on a title where all items have a negative notforloan value (e.g. -1 = "Ordered" — the Koha convention for "not for loan, but holdable"), no reservation fee is charged, even when the applicable circulation rule specifies a hold_fee. The same hold placed on a title where items have notforloan = 0 (available) correctly generates the charge. Steps to Reproduce 1. Configure a circulation rule with a hold_fee for a patron category and item type (e.g. "Adult Fiction Paperback"). 2. Set HoldFeeMode to any_time_is_placed. 3. Create a biblio with one or more items, all with a negative notforloan value (e.g. -1, "Ordered"). 4. Place a hold on that biblio for a patron in the matching category. 5. Observe the patron's account — no reservation fee is applied. Expected: Reservation fee is charged at hold placement, matching the fee that would apply once the item is received. Actual: No fee is charged. The patron can hold the title free of charge for its entire on-order period, then be charged when it arrives — inconsistent and unfair to patrons who paid for the same hold earlier. Root Cause In Koha/Hold.pm, _calculate_title_hold_fee() searches for items to base the fee on using this filter: -or => [ { 'me.notforloan' => 0 }, { 'me.notforloan' => undef } ] This excludes items with negative notforloan values. When all items on a biblio are in an "Ordered" state (negative notforloan), no items match, @fees is empty, and the method returns 0 — causing charge_hold_fee() to skip the charge entirely. However, Koha's own holdability convention (documented in IsAvailableForItemLevelRequest() and CheckReserves()) explicitly states: "item with negative or zero notforloan value is holdable" (notforloan > 0 blocks holds; notforloan <= 0 allows them) The fee calculation code does not follow this same convention, causing the mismatch. Fix Change the notforloan filter in _calculate_title_hold_fee() (Koha/Hold.pm) from matching only = 0 to matching <= 0: # Before -or => [ { 'me.notforloan' => 0 }, { 'me.notforloan' => undef } ] # After -or => [ { 'me.notforloan' => { '<=', 0 } }, { 'me.notforloan' => undef } ] This aligns fee calculation with the holdability logic used consistently elsewhere in the codebase. Test Plan 1. Apply patch. 2. Configure a hold_fee circulation rule for a patron category and item type. 3. Create a biblio with items having notforloan = -1 (Ordered). 4. Place a title-level hold for a matching patron. 5. Confirm a reservation fee is now added to the patron's account. 6. Confirm that items with notforloan = 1 (positive, truly not holdable) still produce no fee. 7. Run prove t/db_dependent/Koha/Hold.t. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 42694] New: Koha produces extra authorities for OCLC fast subject headings
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '26

09 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42694 Bug ID: 42694 Summary: Koha produces extra authorities for OCLC fast subject headings Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: cgresser(a)jesuit.org.uk QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This applies to anyone who imports Marc21 records in the English-speaking world, and who might have standard Library of Congress subject headings, as well as OCLC fast subject headings. After more extra, manual work, the result of what I'm talking about looks like this: 650 _ 0 ‡aMiracles.‡9133027 650 _ 7 ‡aMiracles.‡2fast‡0(OCoLC)fst01023535‡9200794 As this is fairly complicated to explain I have created a screencast (apologies for the low level of sound): https://youtu.be/4hZexR4vmjs What Koha did with the imported bibliographic record's lines 650 _ 0 ‡aMiracles. 650 _ 7 ‡aMiracles.‡2fast‡0(OCoLC)fst01023535 650 _ 0 ‡aMiracles. was initially not synched to the existing "Miracles" subject in local authorities and for 650 _ 7 ‡aMiracles.‡2fast‡0(OCoLC)fst01023535 Koha added an additional OCLC fast subject heading for "Miracles". This meant that there was a third entry for "Miracles" in our authorities. As you can see I could in the video, this can be fixed manually, but this should not be solution. Also, I don't think that one should tell Koha cataloguers in the English-speaking world who use Marc21 to not use the OCLC fast subject headings, which would probably solve the problem). For a while, I had suspected that Koha does this, as I have repeatedly fixed the same, duplicate authorities, in the last 6-8 months, since moving to Koha. This is really a serious inefficiency, and could put off any cataloguer from Koha. Maybe currently Koha does not really look at the indicators (second indicator 0 = Library of Congress, second indicator 7 = scheme specified in subfield 2). Maybe that would be a starting point for allowing several entries with the same basic string of of characters, whilst the actual entry is different...? I would be grateful if other Koha cataloguers in the Marc21 / English-speaking world would like into this, and if I'm missing a solution, please let me know. Many thanks for considering this, Clemens -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5