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

[Bug 38588] New: Checkin that triggers a transfer => print slip => Internal server error
by bugzilla-daemon＠bugs.koha-community.org 17 Apr '25

17 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38588 Bug ID: 38588 Summary: Checkin that triggers a transfer => print slip => Internal server error Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com 1. Check in any item (e.g. 39999000012118) to trigger a transfer. Need to have a home library not in the current library. So it trigger a return-to-home transfer. 2. Print slip. 3. Exception 'Koha::Exceptions::Item::Transfer::InQueue' thrown 'Active item transfer already exists' with transfer => Koha::Item::Transfer=HASH(0x55ef3531c248) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 45

[Bug 25996] New: Changes to debarments should be logged
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '25

16 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25996 Bug ID: 25996 Summary: Changes to debarments should be logged Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com To recreate: 1 - verify borrower log is enabled 2 - click Edit on a patron 3 - on the edit page click "add a manual restriction" and enter a debarred comment, save the patron 4 - click Edit again, remove your restriction 5 - go to patron modification logs, see the log of your changes 6 - go back to the borrower checkout page, click to the Restrictions tab 7 - add a restriction 8 - delete the restiction 9 - go to patron modification logs, see there is not a log of your changes -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 46

[Bug 38397] New: Mandatory requirements in Frameworks need relationship between tag and subfield
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '25

16 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38397 Bug ID: 38397 Summary: Mandatory requirements in Frameworks need relationship between tag and subfield Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This is a followup from Bug 36054 and tested on a 23.11 and 24.05 installation. To recreate: 1. Edit the default framework and uncheck the mandatory box for the SUBFIELD of the 005 and save. The tag itself should still be marked as mandatory. 2. Find a bib record. 3. See the 005 is not required. Save. Note: In 23.11, it is possible to delete data in the 005 and save the record in the basic editor. As of 24.05, saving the record will automatically add data to the 005 in the basic editor if it is missing in the Default framework. The record saves as it should. 4. Now edit the record again and switch to the Advanced Editor. 5. Delete the 005 tag 6. Save. Save fails and gives an error statement "Record structure invalid, cannot save." and "missing mandatory tag: 005." If a tag is marked as mandatory, the subfields should be mandatory. If none of the subfields are mandatory, should the tag still be mandatory? The mandatory requirement highlights a relationship problem between the tag settings and subfield settings. This does raise some questions on how to handle things like the 942$c. This field is mandatory regardless of what the user selects in the framework. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 26170] New: Create "system" patrons that cannot be (easily) deleted via the web ui
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '25

16 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26170 Bug ID: 26170 Summary: Create "system" patrons that cannot be (easily) deleted via the web ui Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement 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 At the moment, the only way to create OAuth2 or Basic Auth credentials is to generate a user. This user can be deleted by a librarian by accident, which will break your API integration with Koha. I propose that we make some system users that cannot be deleted from the Web UI. (Or users that can be deleted by a superlibrarian, but need to be "unlocked" first or maybe have their category changed, and a warning splashed that this will likely break integrations with other systems.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 78

[Bug 31104] New: Pagination generates HTTP "Link:" header which is over 8291 bytes apache's limit
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '25

15 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31104 Bug ID: 31104 Summary: Pagination generates HTTP "Link:" header which is over 8291 bytes apache's limit Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: REST API Assignee: tomascohen(a)gmail.com Reporter: nugged(a)gmail.com CC: tomascohen(a)gmail.com to repeat: 1. Go to /cgi-bin/koha/members/member.pl 2. put this test into the "Search for patron" "Search:" field: "some long test to search in patron fields" 3. Observe "nothing found" but in the server log, it will say (28)No space left on device: [client 127.0.0.1:60330] AH10124: header size is over the limit allowed by ResponseFieldSize (8192 bytes). Bad response header: 'Link: <https://... this of course happens when you searching for something long but seems we came to so long URL which fails to fit into the "forward" (Link: ... header) field, if to debug, it creates a "search" API request URL that is already 5219 bytes long, then this URL is re-encoded and put two times inside the "Link:" header, so it quickly jumps over the 8192 bytes header limit. Note: as we found together that solution in Koha/REST/Plugin/Pagination.pm to split @links in separate "Link:" headers. SIDENOTE: considering that we already have URL 5129 long in this example, we might anyway even without header doubling bump into the 8192 limits (!). We might need re-think later how in general this formed up. Not related to the current shorter fix though. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 17815] New: Problems with search for dateaccessioned
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '25

14 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17815 Bug ID: 17815 Summary: Problems with search for dateaccessioned Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Tested this as described in bug 14861: Search from advanced search by accession date: 2011-09-01 - 2011-09-30 9461 results Searched with SQL: select distinct biblionumber from items where dateaccessioned between '2011-09-01' and '2011-09-30' 805 results The date range search doesn't seem to work right. The search for a single date appears to work correctly. It's also possible to truncate dates using *. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 27945] New: Limit the number of article requests per day per patron category
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '25

14 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27945 Bug ID: 27945 Summary: Limit the number of article requests per day per patron category 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We propose adding an "Article Request Limit" field to the patron category configuration. "Allow __ article requests per day" This limit would be enforced by querying the existing article requests in the database that have been placed during the day and allowing the patron to proceed or deny the request. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 172

[Bug 33292] New: Claim Return doesn't refund lost item charge when MarkLostItemsAsReturned includes "When marking an item as a return claim" and "Refund lost item fee" is on
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '25

11 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33292 Bug ID: 33292 Summary: Claim Return doesn't refund lost item charge when MarkLostItemsAsReturned includes "When marking an item as a return claim" and "Refund lost item fee" is on 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: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using Claim Return, if an item has already been charged as Long Overdue (lost) it does not get refunded when a claim is made, even if lost item fee refund on return policy is set to "Refund" and MarkLostItemsAsReturned includes "When marking an item as a return claim" Since the library is not actually checking the item in it doesn't refund automatically. The library could check the item in and not resolve the claim, but that's an extra step and may not work with all workflows. Having the option to refund the lost fee on claim would be helpful for many libraries. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 37742] New: My virtual card message not showing
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '25

11 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37742 Bug ID: 37742 Summary: My virtual card message not showing Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org If the patron barcode can't be converted into Code39, it should show an error message, but right now there's a coding error. It just shows the following: Error: ${errorMessage} -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 26777] New: Give the user the option to display their patron card barcode from the OPAC
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '25

11 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26777 Bug ID: 26777 Summary: Give the user the option to display their patron card barcode from the OPAC 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 In this modern age, people are moving away from carrying cards.. but they nearly always have their smart phone to hand. It would be nice to be able to display your barcode for scanning at self service machines directly on your phone. -- You are receiving this mail because: You are watching all bug changes.

1 95