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

[Bug 35250] New: Eliminate circular dependencies caused by C4::Context
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35250 Bug ID: 35250 Summary: Eliminate circular dependencies caused by C4::Context Change sponsored?: --- Product: Koha Version: master 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: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Any script using C4::Context is bound to have a huge memory footprint because of the dependencies. And even script that would do without C4::Context (somehow) are bound for the same as soon as they include one Koha:: module, because those will use C4::Context. A graph from v23.05 will summarize it better than any explanation: BackgroundJobs | v BackgroundJob (Net::Stomp : 5M) | | | v | Koha::Object (Mojo::JSON : 16M) v C4::Context (DateTime::TimeZone : 7M) | | (ZOOM : 8M) v | Koha::Config::Syspref | | v | C4::Log (calling back on C4::Context) | | v | Koha::ActionLogs | | v | Koha::ActionLog (calling back on C4::Context) | | v | Koha::Object | | v Koha::Caches (calling back on C4::Context) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 25952] New: Github search for plugin throwing errors for % and koha-plugin search terms
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25952 Bug ID: 25952 Summary: Github search for plugin throwing errors for % and koha-plugin search terms Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org I was trying to get a full list of the available plugins so I tried '%' and 'koha-plugin' as search terms, but they created errors in Koha. Note that the 'koha-plugin' query works directly: https://api.github.com/search/repositories?q=koha-plugin+user:thekesolution… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 39468] New: EDI message status should be case insensitive
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39468 Bug ID: 39468 Summary: EDI message status should be case insensitive Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org There already was a bug (Bug 32676) that should have addressed this. The initial commit looks ok, but the final one, which seems be the one that have been pushed is missing the .lower on edi_order.status. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 39985] New: items.onloan field is not updated when an item is recalled
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39985 Bug ID: 39985 Summary: items.onloan field is not updated when an item is recalled 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: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Depends on: 19532 When an item is recalled, if the due date on the item should be updated due to the recall, only the issues.date_due field gets updated. The due date stored in items.onloan remains unchanged. To replicate: 1. Enable UseRecalls syspref and set corresponding circulation rules: - Recalls allowed - Recalls per record - On shelf recalls allowed - set to "If any unavailable" - Recall due date interval - set to 1 - Recall pickup period 2. Check out an item to a patron 3. Log into the OPAC as another patron 4. Search for the item checked out in step 2 5. Place a recall on that item 6. Search for that item in the staff interface => Note that the item status says, "Checked out to <patron>: due <tomorrow>" 7. Create the following SQL report in the reports module, using the barcode of the item that was recalled: SELECT onloan FROM items WHERE barcode='xxxxxxxxx' 8. Run the report => The onloan value is still set to the item's original due date, not the update due date of tomorrow Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19532 [Bug 19532] Recalls for Koha -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 38516] New: Closed group basket not able to open pdf file with adobe The root object is missing or invalid
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38516 Bug ID: 38516 Summary: Closed group basket not able to open pdf file with adobe The root object is missing or invalid Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org Created attachment 174925 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=174925&action=e… borken pdf We have realizaed from Koha 23.11 and 24.05 adobe is not able to open the pdf, it can be opened via broswer visor, or other pdf reader, but not with Adobe It has been tested wit debian and ubuntu (both SO) I get the error The root object is missing or invalid Test plan 1. Go to acquisition 2. Go to a vender with closed group basket 3. Try to export pdf file 4. Download locally 5. Open with Adobe -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47

[Bug 29908] New: Warning when empty ClaimReturnedWarningThreshold in patron_messages.inc
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29908 Bug ID: 29908 Summary: Warning when empty ClaimReturnedWarningThreshold in patron_messages.inc Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com System preference ClaimReturnedWarningThreshold manages the display of a patron message in case of too many claims. But this preference may be empty. This generates a warning : Argument "" isn't numeric in numeric gt (>) at /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/includes/patron_messages.inc line 128. Default value should be considered has 0 or infinite ? Before Bug 27873 code was in templates, bug still applies. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 39981] New: Patron extended attribute search only available at patrons page
by bugzilla-daemon＠bugs.koha-community.org 20 May '26

20 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39981 Bug ID: 39981 Summary: Patron extended attribute search only available at patrons page 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: mikko.liimatainen(a)turku.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When you have selected patron attribute to be searchable in staff patron searches, this can only be done in the patrons page. However there are many other pages that have the patron search box available where you can't search with the extended patron attributes. I think patron attribute search should be available always when patron search is available. It would be more consistent with the description of the preference. "Check to make this attribute searchable in staff patron searches. If checked, this attribute will appear in patron search dropdowns." -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 39094] New: Adjust system preferences to account for new option to refund the previous lost fee when marking an item Claims returned
by bugzilla-daemon＠bugs.koha-community.org 20 May '26

20 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39094 Bug ID: 39094 Summary: Adjust system preferences to account for new option to refund the previous lost fee when marking an item Claims returned Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 33292 ClaimReturnedChargeFee has the option to charge a lost fee, don't charge, or ask if a lost fee should be charged, when marking an item claims returned. These options should be update to reflect the new option to refund the previous lost item fee. Currently, if the preference is set to "ask if a lost fee should be charged", the modal shows two checkboxes: "Charge a lost fee" and "Refund previous lost fee". If the preference is set to charge or don't charge, the checkbox for "Charge a lost fee" is (correctly) not displayed, but the checkbox for "Refund previous lost fee" is also not displayed. It's a bit odd to show either both checkboxes or neither. It would also be nice to have the same options for refunding the lost fee that we currently have for charging a lost fee (refund, don't refund, or ask). We should add more options to ClaimReturnedChargeFee, or add a ClaimReturnedRefundFee preference. Somewhat relatedly, if we are going to allow the modal to give the user both options to charge or refund (or neither), we should use radio buttons or a drop-down in that case, rather than checkboxes, since it does not make sense to check both at once. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33292 [Bug 33292] 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 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 27919] New: Split Claims Return from LOST
by bugzilla-daemon＠bugs.koha-community.org 20 May '26

20 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27919 Bug ID: 27919 Summary: Split Claims Return from LOST Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be helpful to libraries if Claims Returned was moved out of the Lost Value. It is confusing for patrons and staff to see a Claims Return as a Lost item, and there are times when an item needs to be marked both as Lost and as Claim Return, and combining those into one field can be a challenge. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 62

[Bug 33997] New: Borrowers.updated_on should not be updated by track_login
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33997 Bug ID: 33997 Summary: Borrowers.updated_on should not be updated by track_login 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: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently borrowers.updated_on is updated by track_login even though a login is not an update to the patron record. This update needs to be blocked so that the updated_on field accurately reflects updates to the patron. Logins are supposed to be tracked by borrowers.lastseen which track_login already does. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34