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

[Bug 32441] New: Localuse is recorded in statistics but not recreated in pseudonymized_transactions
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32441 Bug ID: 32441 Summary: Localuse is recorded in statistics but not recreated in pseudonymized_transactions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The pseudonymization feature creates a parallel to the statistics table without identifiable patron data. This allows one to then use cleanup_database to delete old entries in statistics to remove that patron data. However, the statistics table also contains records of local use. That data only exists in statistics. It is not duplicated in pseudonymized_transactions, and so is lost if statistics are deleted using cleanup_database. Bug 32440 suggests teaching cleanup_database to not delete localuse entries. This bug suggests putting localuse entries into pseudonymized_transactions, even though no patron is involved. That's a bit illogical, but has the benefit of keeping all of this data together. Meanwhile, Bug 16122 suggesting keeping a local use count in the item record. That would alleviate this issue somewhat, but specific transactional data would be preferable to a running count. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24841] New: REST API should check if patron is restricted/debarred
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24841 Bug ID: 24841 Summary: REST API should check if patron is restricted/debarred Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no Bug 17247 "ILS-DI HoldTitle and HoldItem should check if patron is restricted" adds checks to see if the patron is restricted before a hold is placed. These checks are added to C4::ILSDI::Services::HoldItem() and C4::ILSDI::Services::HoldTitle(). As far as I can tell, the same checks are missing from the REST API, specifically for "POST /api/v1/holds". Koha::REST::V1::Holds::add() does call C4::Reserves::CanItemBeReserved() and C4::Reserves::CanBookBeReserved(), but as far as I can tell, those subs do not check if the patron in question is debarred. Am I missing something or is this a bug? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 32974] New: Allow different limits for hold the shelf holds vs holds on checked out items
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32974 Bug ID: 32974 Summary: Allow different limits for hold the shelf holds vs holds on checked out items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: rkuiper(a)roundrocktexas.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We would like to see a function in Koha where the hold limit is separated into two limits. One limit for on-the-shelf holds and another limit for holds on items checked out. Currently, we can allow or not allow on-the-shelf holds. We would like to see this expanded to specify the number of holds allowed if we have on-the-shelf holds turned on. Then there would be a separate limit that is for items that are checked out or on order. The reason for separating these is so we can manage staff time on the holds to pull list and still allow patrons to put holds on popular items and items that are new to the library. Our plan would be to allow something like 7 holds for on-the-shelf holds and allow unlimited holds for checked out and on order items. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 35170] New: Make long overdue item type options configurable in interface
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35170 Bug ID: 35170 Summary: Make long overdue item type options configurable in interface Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Being able to set the item type options: 'itemtype=s' => $itemtype 'skip-itemtype=s' => $skip_itemtype, Via the staff interface would be really helpful for users being able to update their longoverdue settings without needing to edit the command line. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 29505] New: Add syspref to allow to place multiple holds on same item
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29505 Bug ID: 29505 Summary: Add syspref to allow to place multiple holds on same item Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.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 6

[Bug 26038] New: Accessibility: 4.1.3 Status Messages
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26038 Bug ID: 26038 Summary: Accessibility: 4.1.3 Status Messages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: oleonard(a)myacpl.org, testopia(a)bugs.koha-community.org Blocks: 23003 The intent of this Success Criterion is to make users aware of important changes in content that are not given focus, and to do so in a way that doesn't unnecessarily interrupt their work. The intended beneficiaries are blind and low vision users of assistive technologies with screen reader capabilities. An additional benefit is that assistive technologies for users with cognitive disabilities may achieve an alternative means of indicating (or even delaying or supressing) status messages, as preferred by the user. The scope of this Success Criterion is specific to changes in content that involve status messages. A status message is a defined term in WCAG. There are two main criteria that determine whether something meets the definition of a status message: https://www.w3.org/WAI/WCAG21/Understanding/status-messages.html Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23003 [Bug 23003] Accessibility improvements -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 39282] New: Receiving orders from a staged/new file leads to 500 errors
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39282 Bug ID: 39282 Summary: Receiving orders from a staged/new file leads to 500 errors Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org TO recreate: 1. In acquisitions create or find a vendor 2. Make a new basket, either from 'New file' or 'Staged file' 3. Receive the order 4. 500 error This is what I see in the logs: ==> /var/log/koha/kohadev/plack-api-error.log <== [2025/03/07 21:25:45] [ERROR] GET /api/v1/acquisitions/orders: unhandled exception (Mojo::Exception)<<Can't call method "bookable" on an undefined value at /kohadevbox/koha/Koha/Item.pm line 1922.>> -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 36978] New: Issue upgrading to v24 from v22 - publishercode
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36978 Bug ID: 36978 Summary: Issue upgrading to v24 from v22 - publishercode Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: rex(a)nicic.gov QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Hi, I'm trying to upgrade from 22.05 to 24 (current). I'm running into this error and I'm not sure how to fix it. I've tried removing the publishercode column from biblioitems and deletedbiblioitems, but it still returns this error. I've also looked at the Installer.pm file, but the error is returning in the middle of a function and I have no idea what to do with that. Any suggestions for how to help get this working again? Upgrading database schema for INSTANCE Upgrade to 23.06.00.007 [21:04:39]: Bug 34029 - Extend datatypes in biblioitems and deletedbiblioitems tables to avoid import errors Updated biblioitems.place to text Updated deletedbiblioitems.place to text ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Can't DROP 'publishercode'; check that column/key exists at /usr/share/koha/lib/C4/Installer.pm line 741 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 38447] New: Fix faulty identity providers
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38447 Bug ID: 38447 Summary: Fix faulty identity providers Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration 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 Depends on: 37157 This is a follow-up from bug 37157: (In reply to Nick Clemens (kidclamp) from comment #7) > One issue is that if I create the provider before this request. this doesn't > fix it. I have to delete them from the database in order to be able to load. > Could we have a DB update to fix/encode existing values? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37157 [Bug 37157] Error 500 when loading identity provider list -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 37157] New: 500 error when loading identity providers on identity_providers.pl
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '25

01 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37157 Bug ID: 37157 Summary: 500 error when loading identity providers on identity_providers.pl Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When we add a new identity provider and put some special characters in the Config or Mapping field, we got 500 error when we list the identity providers -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23