April 2026 - Koha-bugs - lists.koha-community.org

[Bug 42491] New: Debian daily cronjob with cleanup_database.pl should only delete old sessions
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42491 Bug ID: 42491 Summary: Debian daily cronjob with cleanup_database.pl should only delete old sessions Initiative type: --- Sponsorship --- status: 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org In the Debian packages there is a daily cronjob that runs cleanup_database.pl with the --sessions option, which deletes ALL sessions. Typically, the daily cronjob is scheduled to run early in the morning, but it's still a pain for early users of Koha to lose their session due to this cronjob. By default, we should be adding at least --sessdays 1 to the cronjob, so that only sessions that haven't been used for 1 day or were created 1 day ago are cleaned up. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[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 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 --- Comment #46 from David Nind <david(a)davidnind.com> --- I added a couple of follow-ups: - The number of tests was wrong, so the tests failed - The qa script complained about the permissions for the test file - I updated the form label for the option to delete the source bibliographic record (as you can only move items from one record): Delete source bibliographic records if no items remain. To Delete source bibliographic record if no items remain. An observation about the warning, but I don't know if I'm correct or not: - When only a bibligraphic-level hold, the warning is: The source record has 1 biblio-level hold(s). These holds will remain on the source record after the move. - When only an item-level hold, warning is the same. - When there is both a bibliograohic and item-level hold, the warning is also the same: The source record has 2 biblio-level hold(s). These holds will remain on the source record after the move. - Not sure if this needs updating to reflect a bibliographic and item level holds. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 --- Comment #45 from David Nind <david(a)davidnind.com> --- Created attachment 198324 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=198324&action=e… Bug 6532: (follow-up) Update label for deleting source record option As items can only be moved from one record to another, form label updated to "Delete source bibliographic record if no items remain.". Signed-off-by: David Nind <david(a)davidnind.com> -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 --- Comment #44 from David Nind <david(a)davidnind.com> --- Created attachment 198323 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=198323&action=e… Bug 6532: (follow-up) Update the number of tests and permissions Signed-off-by: David Nind <david(a)davidnind.com> -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 --- Comment #43 from David Nind <david(a)davidnind.com> --- Created attachment 198322 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=198322&action=e… Bug 6532: Fix message if only one item left and hold at biblio level Sponsored-by: Université Côte d'Azur Signed-off-by: David Nind <david(a)davidnind.com> -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 --- Comment #42 from David Nind <david(a)davidnind.com> --- Created attachment 198321 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=198321&action=e… Bug 6532: Tidy Sponsored-by: Université Côte d'Azur Signed-off-by: David Nind <david(a)davidnind.com> -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 --- Comment #41 from David Nind <david(a)davidnind.com> --- Created attachment 198320 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=198320&action=e… Bug 6532: Add tests Sponsored-by: Université Côte d'Azur Signed-off-by: David Nind <david(a)davidnind.com> -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 --- Comment #40 from David Nind <david(a)davidnind.com> --- Created attachment 198319 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=198319&action=e… Bug 6532: Add batchMod tool Sponsored-by: Université Côte d'Azur Signed-off-by: David Nind <david(a)davidnind.com> -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '26

29 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 --- Comment #39 from David Nind <david(a)davidnind.com> --- Created attachment 198318 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=198318&action=e… Bug 6532: Way to move items to another record in batches This patch adds a new "Move items in a batch" feature, allowing to move multiple items from one bibliographic record to another in a single operation. Test plan: 1. Apply the patch and restart_all. 2. Open a record with at least 2 items (record A). Open or create a second record (record B). 3. On record A: Edit -> "Move items in a batch". Select 1 item, enter record B's biblionumber, submit. => Job finishes. The item appears on record B, not on record A. 4. Repeat with "Delete source bibliographic records if no items remain" checked and move the last item of record A. => Job finishes. Record A is deleted. 5. Place a biblio-level hold on a record with 2 items (record C). Go to Edit -> "Move items in a batch". => A warning icon appears on each item explaining that biblio-level holds will follow if no items remain. 6. Move only 1 item of record C to record B. => The biblio-level hold stays on record C (still has 1 item). 7. Move the last item of record C to record B. => Job report warns that the biblio-level hold has been automatically transferred to record B. => Confirm: record B now has the hold, record C has none. 8. You can test also with hold at item level. Hold simply follows the item on the new record linked. 9. Try entering a non-existent biblionumber as destination. => Error shown before the job is enqueued. Sponsored-by: Université Côte d'Azur Signed-off-by: David Nind <david(a)davidnind.com> -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0