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

[Bug 34362] New: Progress bar does not progress
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '25

04 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34362 Bug ID: 34362 Summary: Progress bar does not progress Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 31666 Test plan: 1) Go to stage MARC records for import /cgi-bin/koha/tools/stage-marc-import.pl 2) Upload a .mrc file with a couple thousand records 3) Click upload file and then the bottom button "Stage for import" 4) Notice how the bar never progresses, until the job is done successfully. I believe this is because $self->size and $self->progress are both inside $schema->storage->txn_begin and they are not updated in the database in real time until the job is successfully done. I also think $self->progress should be $self->step but I'm not 100% sure about that one. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31666 [Bug 31666] Add job progress bar to stage-marc-import.pl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 41375] New: Tool to generate a default privacy policy document
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '25

04 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41375 Bug ID: 41375 Summary: Tool to generate a default privacy policy document Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org It would be nice to ship a default privacy policy document with Koha. It could be a configurable tool where superlibrarians could 1. check checkboxes for the types of data they are collecting in Koha 2. include the values of *Log system preferences 3. include templates from privacy regulations, such as GDPR, or national legislation (you could select which template to add) 4. define the durations of data collection (it would be nice to be able to read the triggers of cleanup-database.pl and other cronjobs, but this shouldn't be a blocker for this Bug) 5. document the use of cookies https://wiki.koha-community.org/wiki/Use_of_Cookies The tool would come with prewritten templates, but they should also be modifiable. Something like we currently have with notice templates. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39532] New: Script debar_patrons_with_fines.pl creates repeat restrictions, uses wrong restriction type
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '25

04 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39532 Bug ID: 39532 Summary: Script debar_patrons_with_fines.pl creates repeat restrictions, uses wrong restriction type Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The cronjob debar_patrons_with_fines.pl is meant to add a restriction based on a fines threshold. The problem is that the script adds a MANUAL restriction, which makes no sense. MANUAL restrictions are meant to be manually created, never automatic as this script does. In addition, they are repeatable, not unique. Every time this script runs, it will add an additional restriction. There is already a restriction type meant for this type of use case: SUSPENSION We should change this script to create SUSPENSION restrictions instead of MANUAL restrictions. In summary, this script should use the unique restriction type SUSPENSION to prevent multiple additional restrictions from being created on each run. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 33660] New: Allow editing "Create items when" when no orders have been created
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '25

04 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33660 Bug ID: 33660 Summary: Allow editing "Create items when" when no orders have been created Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When a new basket is created, the "Create items when" can be set. But: Once the basket has been saved, this filed is missing from the form. Suggestion: * Allow editing of the field when no orders have been created yet. * When orders exist, show the field as read only with a hint to avoid questions/confusion. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 41374] New: Display "create items when" in general basket information
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '25

04 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41374 Bug ID: 41374 Summary: Display "create items when" in general basket information Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: esther.melander(a)bywatersolutions.com Moved from bug 33660: It would be nice if the "Create items when" displayed in the General information about the basket. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 41168] New: "Search the catalog by keyword" confuses some users
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '25

04 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41168 Bug ID: 41168 Summary: "Search the catalog by keyword" confuses some users Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org We got some questions about this new test from masthead on the OPAC search bar. Like: Can I only use keywords now? I would propose to remove the phrase "by keyword" here. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 30633] New: Move OPACHoldingsDefaultSortField to table settings configuration
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '25

04 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30633 Bug ID: 30633 Summary: Move OPACHoldingsDefaultSortField to table settings configuration 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 29648 Now that the sorting of a table can be defined in administration > table settings, we should move OPACHoldingsDefaultSortField there and remove the pref. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29648 [Bug 29648] Make KohaTable tables 'default length' and 'default sort' configurable -- You are receiving this mail because: You are watching all bug changes.

1 61

[Bug 41372] New: Preservation/Settings.ts is failing
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '25

04 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41372 Bug ID: 41372 Summary: Preservation/Settings.ts is failing Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org There is a warning in the console: > JS Warning detected: "[Vue warn]: Unhandled error during execution of setup function" "\n" " at <RouterLink" "key=1" "to=\"/cgi-bin/koha/preservation/settings/processings\"" ">" "\n" " at <NavigationItem" "key =0" "item=" [object Object] "params=" {} ">" "\n" " at <Breadcrumbs>" "\n" " at <App>" -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 9810] Search limit 'available' does not hide damaged, withdrawn, or not-for-loan items
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '25

03 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9810 Katie Bliss <kebliss(a)dmpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kebliss(a)dmpl.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 40743] New: Unable to select the correct fund when paying invoices.
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '25

03 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40743 Bug ID: 40743 Summary: Unable to select the correct fund when paying invoices. Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: tgoatley(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 186059 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=186059&action=e… Display of order edit We are an early adopter to 25.05.02 and we're unable to select the correct fund when paying invoices. This refers to paying paper invoices we receive since as this Baker &Taylor example. Previously, we were given the option to select the fund, and since we have two active funds now due to closing out the fiscal year, we are only able to see one of the active funds (unfortunately not the fund we need to pay this invoice). I checked acquisitions permissions, and Sandra has full ACQ permissions. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36