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

[Bug 19316] New: Items should have sort1 and sort2 fields
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19316 Bug ID: 19316 Summary: Items should have sort1 and sort2 fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Librarians love data, like for real, they can't get enough. We often find that libraries want extra information in their items table, things that don't fit or don't belong in any of the existing columns. Borrowers have sort1 and sort2 for this kind of information - we should add analogous fields to the items table -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 55

[Bug 27115] New: Restarting koha-common fails to restart SIP2 server
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27115 Bug ID: 27115 Summary: Restarting koha-common fails to restart SIP2 server Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com Sometimes when we run "systemctl restart koha-commmon" the SIP server doesn't get restarted but might just get stopped leading to longer than expected downtime. There is probably some sort of race condition. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 28308] New: Select 'Days in advance' = 0 for Advance notice effectively disables PREDUE notices
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28308 Bug ID: 28308 Summary: Select 'Days in advance' = 0 for Advance notice effectively disables PREDUE notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Looking at the code below, it seems that on the day an item is due we will only send the DUE notices, predues will not be sent In the advance_notices.pl cron: 276 if ( 0 == $upcoming->{'days_until_due'} ) { 277 # This item is due today. Send an 'item due' message. ... 323 } else { 324 $borrower_preferences = C4::Members::Messaging::GetMessagingPreferences( { borrowernumber => $upcoming->{'borrowernumber'}, 325 message_name => 'advance_notice' } ); 326 next UPCOMINGITEM unless $borrower_preferences && exists $borrower_preferences->{'days_in_advance'}; 327 next UPCOMINGITEM unless $borrower_preferences->{'days_in_advance'} == $upcoming->{'days_until_due'}; In this case, allowing the user to choose '0' is effectively disabling the notice. I think we need to remove 0 as an option, and uncheck all transports for patrons who have '0' set for days in advance -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 20846] New: Suppressed Records Still Appear in Public Lists
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20846 Bug ID: 20846 Summary: Suppressed Records Still Appear in Public Lists Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To test: 1. Add a title to a public list 2. Edit the 942$n to suppress the record 3. Confirm that the record isn't visible in the opac 4. Confirm that the title still shows in the list It'd be great to have suppressed records hidden from lists. Even if the link from the list to the bib takes the user to the blocked record page, showing the title in the list is confusing. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 40225] New: The --send-all option in the stockrotation job fails if there are no items to rotate at all
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40225 Bug ID: 40225 Summary: The --send-all option in the stockrotation job fails if there are no items to rotate at all Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The send-all option claims to send notices even if there are no items to rotate for the given branch; However, if there are no items to action anywhere on the system we skip all notices entirely, not respecting the send-all option. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 27138] New: Host items are not included in Z39 results when using EasyAnalytics
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27138 Bug ID: 27138 Summary: Host items are not included in Z39 results when using EasyAnalytics Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 If a library enables EasyAnalytics and links two records in the catalog then the host items show on the child record. If you search for these records via Z3950 (via zebra directly or the responder) the host items are not shown -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 61

[Bug 32734] New: REST API: Add a list endpoint for Biblios
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32734 Bug ID: 32734 Summary: REST API: Add a list endpoint for Biblios Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com CC: tomascohen(a)gmail.com In addition to being able to GET a specific biblio, we should be able to search and retrieve subsets of biblios -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 39977] New: Prevent reserves of items the users have already on their possession
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39977 Bug ID: 39977 Summary: Prevent reserves of items the users have already on their possession 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: adolfo.rodriguez(a)xercode.es QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When the system preference AllowHoldsOnPatronsPossessions is set to Allow users can request holds on biblio records they have items checked out from. That includes the very items they already have in their possession. I think Koha should check at the item level that you don't already have this item. As I see this system preference, it should only allow to request a hold on the other items. For example, the bibliographic record is a manga series of several volumes. The user has checked the first volume, the system should let them to put a hold on the second volume, but not on the first one. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 36934] New: "Wrong CSRF" after login rejection (StaffLoginRestrictBranchByIP)
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36934 Bug ID: 36934 Summary: "Wrong CSRF" after login rejection (StaffLoginRestrictBranchByIP) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 36933 Found when testing StaffLoginRestrictBranchByIP: * Turn on StaffLoginRestrictBranchByIP * Set CPL's IP to 1.2.3.4 * Go to the staff login screen and try to connect to CPL => Error: Autolocation is switched on and you are logging in with an IP address that doesn't match your library. (OK) * Pick another library => 403 (KO) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 37041] New: Logging into addbiblio.pl triggers a 403
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37041 Bug ID: 37041 Summary: Logging into addbiblio.pl triggers a 403 Change sponsored?: --- 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org As Michal Kula noted on Mattermost, trying to log into http://localhost:8081/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=99… in main will yield a bizarre HTTP response that includes headers for a 403 response and a 200 response... This is partially due to bug 37040, but it's mostly due to a bug in addbiblio.pl where the form builder is generating a 403 that gets printed before the 200 response somehow... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 79