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

[Bug 40554] New: Improve performance using a cache for AV descriptions
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40554 Bug ID: 40554 Summary: Improve performance using a cache for AV descriptions Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We are retrieving the authorised values from the DB whereas they can be stored in a cache. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 37978] New: Internal server error in upload-cover-image.pl
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37978 Bug ID: 37978 Summary: Internal server error in upload-cover-image.pl Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: egpetridis(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 171845 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=171845&action=e… intranet-error.log Error "Internal Server Error" is raised/shown on screen when one tries to upload local cover image in a new (migrated to a new server) koha installation. Relevant log contents attached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 32059] New: How to run scripts found under https://perldoc.koha-community.org/
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32059 Bug ID: 32059 Summary: How to run scripts found under https://perldoc.koha-community.org/ Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mik(a)adminkuhn.ch QA Contact: testopia(a)bugs.koha-community.org Documentation pages like https://perldoc.koha-community.org/misc/migration_tools/bulkmarcimport.html do not give the proper command to run the script. In the example section "Usage" says: $ export KOHA_CONF=/etc/koha.conf $ perl misc/migration_tools/bulkmarcimport.pl -d -commit 1000 -file /home/jmf/koha.mrc -n 3000 When using Debian package installation one way to actually run the program is: As user "root": # export KOHA_CONF=/etc/koha/sites/instancename/koha-conf.xml # export PERL5LIB=/usr/share/koha/lib # /usr/share/koha/bin/migration_tools/bulkmarcimport.pl -b -m marcxml -framework=frameworkname -file TITEL.marcxml -v 2 But it seems the following way is recommended: As user "koha": $ sudo koha-shell -c "/usr/share/koha/bin/migration_tools/bulkmarcimport.pl -b -m marcxml -framework=frameworkname -file TITEL.marcxml -v 2" instancename Better documentation how to run this kind of scripts would be useful. https://perldoc.koha-community.org/ shows many more such scripts. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 41299] New: Add the option to record 'Banked' amounts in cash management
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41299 Bug ID: 41299 Summary: Add the option to record 'Banked' amounts in cash management Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Point of Sale Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk The cashup workflow currently assumes you will 'Bank' all the 'Bankable' cash from a transaction session. However, in some cases, the bank will not accept certain denominations being paid in and so you want the option to record the actual amounts banked and roll forward any surplus to the next bankable session. This is of particular interest to British libraries banking via the Post Office. The Post Office will only accept, for example, £10 worth of 50p coins at a time.. if you have collections £13.50 in 50p coins you will only be allowed to bank £10 worth of them and need to replace the excess £3.50 into the register for banking in the next cashup. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 42669] New: es_indexer_daemon.pl silently marks jobs finished on indexing failure and doesn't recover from NoNodes
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42669 Bug ID: 42669 Summary: es_indexer_daemon.pl silently marks jobs finished on indexing failure and doesn't recover from NoNodes Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 39769 es_indexer_daemon.pl has two issues that cause silent data loss: 1. When update_index() throws an exception (e.g. NoNodes, BadResponse), the exception is caught and logged, but the job is still marked status='finished'. This means records are never re-indexed and silently disappear from search results. 2. The Search::Elasticsearch client (cxn_pool=Static) marks nodes as 'dead' after a connection failure and applies exponential backoff up to 60 minutes. Since the indexer objects are created once at daemon startup, a brief ES restart (e.g. Docker upgrade) leaves the daemon permanently stuck in NoNodes state until manually restarted. Fix: - On NoNodes: abort the batch, recreate the indexer object (resetting the connection pool), and reset jobs to status='new' for automatic retry. - On other indexing errors: mark jobs as 'failed' instead of 'finished'. Test plan: 1. Start es_indexer_daemon.pl 2. Stop Elasticsearch 3. Add/modify a biblio record (triggers indexing job) 4. Verify the job stays in status='new' (not 'finished') 5. Restart Elasticsearch 6. Verify the job is picked up and indexed successfully Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39769 [Bug 39769] es_indexer_daemon.pl uses stale L1 cache -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 38345] New: Remove support for OpenSearch
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38345 Bug ID: 38345 Summary: Remove support for OpenSearch Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Truth is our test suite has been exploding consistently when trying to launch OpenSearch: * https://jenkins.koha-community.org/job/Koha_Main_OS2/ * https://jenkins.koha-community.org/job/Koha_Main_OS1/ This has some precedent discussion on [issue 429](https://gitlab.com/koha-community/koha-testing-docker/-/issues/429) in `KTD` project issues. We are not going to remove it, I guess. But some noise is needed as people using OpenSearch in production don't seem to care we are not being able to run the test suite, so probably promising some 'OpenSearch support' that we cannot guarantee in any way. And if there's a problem with OpenSearch, we (devs) cannot launch a working environment to fix/test. My two cents on this matter. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 71

[Bug 41959] New: Holds queue builder doesn't always check all holds when using transport cost matrix
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41959 Bug ID: 41959 Summary: Holds queue builder doesn't always check all holds when using transport cost matrix Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests 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, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com The scenario presented itself under a specific circumstance Library A ordered a copy of a book and left in 'on order' status Library B purchased a copy and made it available Each library can only fill holds on their own items The transport cost matrix only allows items to transfer to their own branch The transfer limits only allows items to transfer to their own branch A patron of Library A places a title level hold, it can't fill because library A's item is unavailable (on order) A patron of Library B places a title level hold, it should be queued for library B's item In C4::HoldsQueue::MapItemsToHoldRequests we call _allocateWithTransportCostMatrix In _allocateWithTranportCostMatrix we have this code: if ( $num_tasks > $num_agents ) { @remaining = @requests[ $num_agents .. $num_tasks - 1 ]; @requests = @requests[ 0 .. $num_agents - 1 ]; $num_tasks = $num_agents; } task = requests and agents = items In our scenario - 2 tasks/requests and 1 item/agent The code above drops the second request, and sets tasks to 1 We then loop tasks and agents: for ( my $i = 0 ; $i < $num_agents ; $i++ ) { for ( my $j = $r ; $j < $num_tasks ; $j++ ) { But since we have dcereased things above, we only check the first task/request - the second hold, which should be filled, is never checked -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 22160] New: OMNIBUS: Transfers enhancements
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '26

05 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22160 Bug ID: 22160 Summary: OMNIBUS: Transfers enhancements 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 91

[Bug 42214] New: ERM usage database table erm_usage_yus contains incorrect data
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '26

05 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42214 Bug ID: 42214 Summary: ERM usage database table erm_usage_yus contains incorrect data Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: michaela.sieber(a)kit.edu QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, pedro.amorim(a)openfifth.co.uk There is an issue with the calculation of yearly usage: the yearly totals should equal the sum of all monthly usage values, but they currently do not. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 41305] New: Make the list of harvesting jobs more informative in erm/eusage/usage_data_providers
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '26

05 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41305 Bug ID: 41305 Summary: Make the list of harvesting jobs more informative in erm/eusage/usage_data_providers Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, pedro.amorim(a)openfifth.co.uk I have not checked in main, but in 24.11 when you harvest a datasource this kind of message is displayed : "Job for report type DR has been queued. Check job progress." It could be more informative : adding the name of the source and the begin and end date could make it easier to identify a job if you want to get more information -- You are receiving this mail because: You are watching all bug changes.

1 8