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

[Bug 38737] New: Batch item deletion w/delete record broken
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '26

30 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38737 Bug ID: 38737 Summary: Batch item deletion w/delete record broken 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To reproduce in koha-testing-docker (I started it wirh "ktd --es7 up"): - Find a record with at least one item - Click on "Select all" for the items - Click on "Delete selected items" - Click the checkbox for "Delete records if no items remain." - Click on "Delete selected items" - Click on "View detail of the enqueued job" - The job failed Logs: ==> /var/log/koha/kohadev/worker-output.log <== {UNKNOWN}: An Elasticsearch error occurred during bulk delete at /kohadevbox/koha/Koha/BackgroundJob/BatchDeleteItem.pm line 153. at /kohadevbox/koha/Koha/BackgroundJob/BatchDeleteItem.pm line 177 [2024/12/18 08:55:39] [WARN] Uncaught exception processing job id=9: encountered object '{UNKNOWN}: An Elasticsearch error occurred during bulk delete at /kohadevbox/koha/Koha/BackgroundJob/BatchDeleteItem.pm line 153. at /kohadevbox/koha/Koha/BackgroundJob/BatchDeleteItem.pm line 177 ', but neither allow_blessed, convert_blessed nor allow_tags settings are enabled (or TO_JSON/FREEZE method missing) at /kohadevbox/koha/Koha/BackgroundJob.pm line 270. main::catch {...} /kohadevbox/koha/misc/workers/background_jobs_worker.pl (206) The job in the database: MariaDB [koha_kohadev]> select * from background_jobs where id = 9\G *************************** 1. row *************************** id: 9 status: failed progress: 0 size: 4 borrowernumber: 51 type: batch_item_record_deletion queue: long_tasks data: {"delete_biblios":"on","record_ids":["27","24","25","26"]} context: {"number":"51","register_name":null,"shibboleth":"0","branch":"CPL","cardnumber":"42","flags":"1","desk_name":null,"register_id":null,"emailaddress":null,"interface":"intranet","desk_id":null,"surname":"koha","id":"koha","firstname":null,"branchname":"Centerville"} enqueued_on: 2024-12-18 08:55:39 started_on: 2024-12-18 08:55:39 ended_on: NULL 1 row in set (0.000 sec) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 35957] New: Does Serial module still allow saving 0000-00-00 in database?
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '26

30 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35957 Bug ID: 35957 Summary: Does Serial module still allow saving 0000-00-00 in database? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Seeing two issues in 22.11 with invalid/empty date fields: [1] Exception 'Koha::Exceptions::WrongParameter' thrown 'Invalid date '00-1-11-30' passed to output_pref' Crash in output_pref comes from serials/subscription-add.pl line 405 $nextacquidate = $nextacquidate ? output_pref( { str => $nextacquidate, dateonly => 1, dateformat => 'iso' } ) : $firstacquidate; So it received a 0000-00-00. [2] Receive step on serial collection. Save issue without filling dates: | 9531 | 156662 | 318 | No. 12 | 11 | 0 | 0 | 1 | 0000-00-00 | | 0000-00-00 | | NULL | 0 | NULL | Planned and publisheddate were NULL but are now 0000-00-00. Did not check master. Probably still the same? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 40151] New: Make SeparateHoldings work again
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '26

30 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40151 Bug ID: 40151 Summary: Make SeparateHoldings work again Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org To reproduce in KTD: - SeparateHoldings = Separate - Find a record with items from more than one library, for example "The definitive guide to Catalyst" - View the detail page - No items are displayed and the "Processing ..." spinner spins indefinitely -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 39422] New: Checkout 'remember for session' override does not handle holds cancellation
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '26

30 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39422 Bug ID: 39422 Summary: Checkout 'remember for session' override does not handle holds cancellation 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: nick(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 - Place several holds for patron A 2 - Checkout one of the items to Patron B 3 - You get a warning with an option to cancel the hold 4 - Check the cancel button and the remember button 5 - Checkout the rest of the held books 6 - No warnings 7 - Check patron A - only the first hold was cancelled We have situations where a caregiver or relative will pickup the holds for a patron and the libraries would like to see all of the holds cancel - i.e. we need to remember the saved options correctly -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 37638] New: Link permissions to entry in the manual
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '26

30 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37638 Bug ID: 37638 Summary: Link permissions to entry in the manual 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: lauren_denny(a)sil.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Similar to bug 37624, create a link by the permission that takes you to the manual. If applicable, it would also be helpful to put a note by the permission if a system preference is required. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 20844] New: Reset a hold when it is missing after allocation
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20844 Bug ID: 20844 Summary: Reset a hold when it is missing after allocation 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: hughr(a)brimbank.vic.gov.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There currently is no simple way to 'deallocate' a hold if it has gone missing after it is allocated to a patron but before they collect it. This enhancement would work as follows: 1. item is allocated 2. item cannot be located when patron tries to collect it 3. staff member marks item as Lost 4. if hold was originally a bib-level hold, hold reverts from being specific to the missing item, back to a bib-level hold with priority 1. 5. if hold was originally item-level, staff member gets an alert asking whether to cancel or retain the hold 6. (optionally?) a 'lost hold' notice is queued to be sent to the patron This bug is related to the original description of https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19287#c32 and also to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15679 To do it properly, it may require a couple of new settings, something like: LostBibLevelHoldsRevert SendLostHoldNotices -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 150

[Bug 38399] New: Create a script that lists records that are not linked to any authority
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38399 Bug ID: 38399 Summary: Create a script that lists records that are not linked to any authority Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: enica(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz It would be nice to have a script that would list which bibliographic records are not linked to any authorities. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 38327] New: 403 errors when logging back into Koha.
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38327 Bug ID: 38327 Summary: 403 errors when logging back into Koha. Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Firstly, I have been unable to recreate this issue myself, either in a production environment or in k-t-d. Many libraries are reporting 403 errors after signing back into Koha. The only remedy seems to be clearing the browser cache. This is happening to sessions in the staff client but also happening frequently in the SCO module. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 39730] New: Remove GetUnprocessedSuggestions from C4/Suggestions.pm
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39730 Bug ID: 39730 Summary: Remove GetUnprocessedSuggestions from C4/Suggestions.pm 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: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23990 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 39716] New: Warn when saving a notice with template toolkit errors
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '26

28 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39716 Bug ID: 39716 Summary: Warn when saving a notice with template toolkit errors Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When a notice is saved with unusable template toolkit, we should warn even if not using the "save and continue editing" button, such as redirecting back to the page with the error. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5