December 2024 - Koha-bugs - lists.koha-community.org

[Bug 37187] New: 2 problems with label batches
by bugzilla-daemon＠bugs.koha-community.org 21 Feb '25

21 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37187 Bug ID: 37187 Summary: 2 problems with label batches Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: isabel.pineda(a)ds.edu.sv QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl After updating from version 23.11 to 24.05, I found 2 problems with label batches: 1. In the item view of a book, the option "Actions > Print label" is not working anymore. I have to go to the Cataloging module to create a new label batch from there. 2. I cannot delete label batches anymore: The "Delete"-button in the list of label batches is not working. And inside the label batch, the button "Delete label batch" is not working either. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 37080] New: Cannot delete a MARC bibliographic framework
by bugzilla-daemon＠bugs.koha-community.org 21 Feb '25

21 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37080 Bug ID: 37080 Summary: Cannot delete a MARC bibliographic framework Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl On current main (and 24.05) you cannot delete a MARC bibliographic framework. Reported on chat (13 June 2024) for 24.05.00 and reproduced on main. Steps to reproduce: 1. Go to Koha administration > Catalog > MARC bibliographic frameworks. 2. For a framework, select Actions > Delete. 3. Message displayed: "Confirm deletion of framework '' ()?" (with options under this - "Yes, delete this framework" and "No, do not delete") (note that the URL has the framework code /cgi-bin/koha/admin/biblio_framework.pl?op=delete_confirm&frameworkcode=ACQ) 4. Click "Yes, delete this framework". 5. Error message displayed: "An error occurred when deleting this framework. Check the logs for details." 6. Nothing in the logs that seems of any help (/var/logs/koha/kohadev/* - where kohadev is the instance name). Other observations: 1. If you create a new framework (without adding any MARC structure) and attempt to delete, you get the same error. So not related records using the framework. 2. No JavaScript or other browser console errors using the browser's web development tools. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 37093] New: 403 Forbidden Error when attempting to search for Mana Reports
by bugzilla-daemon＠bugs.koha-community.org 21 Feb '25

21 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37093 Bug ID: 37093 Summary: 403 Forbidden Error when attempting to search for Mana Reports Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Mana-kb Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com CC: alex.arnaud(a)biblibre.com We are running 24.05 and have found then when we attempt to search the Mana kb for a report, we are getting a 403 Forbidden Error. Steps to reproduce: 1. have mana set up 2. Go to reports, create a new report from mana 3. Use a term to search 4. receive a 403 forbidden error. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 37069] New: Authorities pagination on OPAC broken by CSRF
by bugzilla-daemon＠bugs.koha-community.org 21 Feb '25

21 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37069 Bug ID: 37069 Summary: Authorities pagination on OPAC broken by CSRF 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 36597] New: Cannot delete circulation desk
by bugzilla-daemon＠bugs.koha-community.org 21 Feb '25

21 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36597 Bug ID: 36597 Summary: Cannot delete circulation desk Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: System Administration Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 36192 Our CSRF work introduced a problem with deleting circulation desks: The "delete_confirm" does not need "cud-" because it's a GET operation leading to a POSTed deletion after the confirmation is submitted. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36192 [Bug 36192] [OMNIBUS] CSRF Protection for Koha -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 37489] New: Cannot delete patron image without uploading a file
by bugzilla-daemon＠bugs.koha-community.org 21 Feb '25

21 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37489 Bug ID: 37489 Summary: Cannot delete patron image without uploading a file Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We've got the upload file field as a required field for patron image, which means that if you try to delete the existing patron image... it won't work because it'll prompt you to upload an image. Basically there is 1 HTML form and there should be 2. Should be an easy fix, but I'm not working on it currently. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 32498] New: Checking an in-transit item out at a branch other than the tobranch should cancel the transfer rather than complete it
by bugzilla-daemon＠bugs.koha-community.org 21 Feb '25

21 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32498 Bug ID: 32498 Summary: Checking an in-transit item out at a branch other than the tobranch should cancel the transfer rather than complete it 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: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If an item is mid-transfer and gets checked out at a branch other than its tobranch, Koha marks the transfer as arrived and edits the tobranch to be the branch at which the checkout happens. This makes for a confusing data trail. Instead, the transfer should be cancelled and the original tobranch should be retained. https://github.com/Koha-Community/Koha/blob/c7a995d28f7ae3759ec9ad377b5f7f2… To recreate: 1: Start a manual transfer of an item from Branch A to Branch B 2: Confirm the item shows as in transit and the branchtransfers table shows frombranch=A, tobranch=B 3: Check item out at Branch A 4: Confirm the branchtransfers table now shows frombranch=A, tobranch=A, has a datearrived value, and has a comment "Forced branchtransfer" (or, if the checkout happens at a third branch) 5: Start a manual transfer of an item from Branch A to Branch B 6: Confirm the item shows as in transit and the branchtransfers table shows frombranch=A, tobranch=B 7: Check item out at Branch C 8: Confirm the branchtransfers table now shows frombranch=A, tobranch=C, has a datearrived value, and has a comment "Forced branchtransfer" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 32438] New: Pseudonymized_transactions should include payments and writeoffs
by bugzilla-daemon＠bugs.koha-community.org 21 Feb '25

21 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32438 Bug ID: 32438 Summary: Pseudonymized_transactions should include payments and writeoffs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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 Depends on: 24151 The pseudonymization process aims to duplicate the transactional circulation data from the statistics table in a way that does not allow borrowers to be identified. The statistics table also includes entries for payments and writeoffs that contain the borrowernumber of the impacted patron. We should also record payments and writeoffs in pseudonymized_transactions when pseudonymization is enabled. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24151 [Bug 24151] Add a pseudonymization process for patrons and transactions -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 38635] New: Improve place hold confirmation page in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 21 Feb '25

21 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38635 Bug ID: 38635 Summary: Improve place hold confirmation page in the OPAC Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Created attachment 175244 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=175244&action=e… Screenshot of the current hold confirmation screen I think the current design of the OPAC's hold confirmation page is a little confusing, or at least cluttered. We have the heading "Placing a hold" and then a redundant (at least for sighted users) "Place a hold on" label next to the checkbox. I think we can clean it up a little. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 38224] New: Move populate_empty_callnumbers logic into Koha::Biblio for reusability
by bugzilla-daemon＠bugs.koha-community.org 21 Feb '25

21 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38224 Bug ID: 38224 Summary: Move populate_empty_callnumbers logic into Koha::Biblio for reusability Change sponsored?: --- 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 Bug 34784 introduced an endpoint for populating empty item callnumbers. In order to be able to create a CLI script for the same purpose, it would be positive to migrate that code into Koha::Biblio. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12