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

[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 39203] New: Remove checkbox to Apply format settings to all notices
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '25

15 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39203 Bug ID: 39203 Summary: Remove checkbox to Apply format settings to all notices Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: lucas(a)bywatersolutions.com Depends on: 35267 When editing a notice, one can enter CSS in the Format section to customize the notice when printed. This includes a checkbox to make the CSS entered in one notice apply to all notices printed by the system. This presents a support challenge, as any CSS used in this fashion is applied very broadly and not easily found when it needs to be edited. Bug 35267 adds system preferences for CSS to be applied to all notices based on transport type. Those system preferences will duplicate the functionality offered by this checkbox. As such, I'd like to remove the option to apply CSS saved in a single notice to other notices in the system. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35267 [Bug 35267] Clarify CSS options for Notices -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[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 39481] New: It would be good to have validation on the patron self registration for date of birth
by bugzilla-daemon＠bugs.koha-community.org 15 Apr '25

15 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39481 Bug ID: 39481 Summary: It would be good to have validation on the patron self registration for date of birth Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org It's sometimes easy to enter an incorrect character and result in entering a date of birth making you a few hundred years old.. we should add the option to validate that a data of birth is within the last 100 years or similar to prevent 1800's birthdays ;) -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 39275] New: Merging records can destroy records if page has not fully loaded
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '25

14 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39275 Bug ID: 39275 Summary: Merging records can destroy records if page has not fully loaded Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We just had a case where a lot of records where merged while the instance was slowed down significantly (crawlers) and the records ended up emptied out completely. As far as we can tell, this is what happened: * Select 2 records to merge from catalog or cataloguing search * Select "winner" record * On the next page, the second column with the "winner" is loaded a little after the rest of the page -> When you merge before it's loaded, the record is emptied out -> Wait until the page is fully loaded, the record will be ok. Maybe we could lock the "Merge records" button, until the page is fully loaded? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[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