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

[Bug 39522] New: Add hooks to allow 'Valuebuilder' plugins to be installable
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '26

06 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39522 Bug ID: 39522 Summary: Add hooks to allow 'Valuebuilder' plugins to be installable Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: jacob.omara(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org We should allow the cataloguing or 'valuebuilder' plugins to be installable with the standard plugin architecture. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 72

[Bug 35092] New: [OMNIBUS] Remaining background job/worker issues
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '26

06 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35092 Bug ID: 35092 Summary: [OMNIBUS] Remaining background job/worker issues 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org 32305 Background worker doesn't check job status when received from rabbitmq 33334 koha-worker.service need update for background job queues 34477 Further reduce memory usage for idle background job worker 34990 34997 Let me add a few more. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 64

[Bug 35920] New: Centralize code from workers
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '26

06 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35920 Bug ID: 35920 Summary: Centralize code from workers 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+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 35819 With bug 35819 we will have too much code duplicated in worker scripts. It needs to be moved to a module. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35819 [Bug 35819] "No job found" error for BatchUpdateBiblioHoldsQueue (race condition) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 61

[Bug 42077] New: Move RabbitMQ from mandatory to optional and make SQL polling the default
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42077 Bug ID: 42077 Summary: Move RabbitMQ from mandatory to optional and make SQL polling the default Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 41506 On bug 41506 we discussed the option of removing RabbitMQ from the codebase. There appears to be consensus that a sensible first step is to update packages to make RabbitMQ optional and SQL polling the default. I believe this would still allow libraries to use RabbitMQ and even move it to a separate server without it installing on the Koha server. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41506 [Bug 41506] Should we remove RabbitMQ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 26197] New: Using Rancor while cataloging doesn't appear to check for existing records
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26197 Bug ID: 26197 Summary: Using Rancor while cataloging doesn't appear to check for existing records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Upon testing this, while cataloging a new record using the basic editor Koha will find a duplicate record existing in Koha but didn't find the same duplicate using the Advanced Editor. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 43196] New: PUT requests with a bad request body to biblios endpoint blanks a record
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43196 Bug ID: 43196 Summary: PUT requests with a bad request body to biblios endpoint blanks a record Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Target Milestone: --- TO recreate: 1. Have a record in Koha with good MARC data. In KTD I'm using biblionumber=32 as an example. 2. Do a PUT requested with invalid JSON in it. I did this: curl -u koha:koha -X PUT http://localhost:8081/api/v1/biblios/32 -H "Content-Type: application/marc-in-json" -H "Accept: application/json" -d '{"leader":"00000nam a2200000 a 4500","fields":[{"245":{"ind1":"1","ind2":"0","subfields":[{"a":"STOP HERE ON PURPOSE!!!' 3. The response is 200, success. 4. Now go look at the record in Koha. It is contains nothing in the MARC record now. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 38666] New: New feature: closed stack requests
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38666 Bug ID: 38666 Summary: New feature: closed stack requests Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com A closed stack request is a special kind of hold that can only be placed on a closed stack item. A closed stack item is an item that is not available publicly in the library but can be made available on demand. When a request is made, a librarian will print a slip then will go retrieve the document and place the slip in place of the document. -- You are receiving this mail because: You are watching all bug changes.

1 88

[Bug 42832] New: Introduce a basic theme step to onboarding tool
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42832 Bug ID: 42832 Summary: Introduce a basic theme step to onboarding tool Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- When we set up a new small Koha there's a few common steps we'll do that make the Koha feel more like their own and work more seamlessly: - set OPACBaseURL and staffClientBaseURL system preferences - set LibraryName system preference - provide a logo or banner image URL to place on the OPAC - provide a primary colour to use for headings and links on the OPAC It would be nice if these steps could be done as part of the onboarding process -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 42807] New: Introduce profiles to onboarding tool to pre-set preferences and other settings based on type of installation
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42807 Bug ID: 42807 Summary: Introduce profiles to onboarding tool to pre-set preferences and other settings based on type of installation Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- The Koha Administration module holds hundreds of possible settings and configurations. The web installer now has an onboarding tool which sets the critical things up from the beginning - but then what? We'd like to introduce 'profiles' to the onboarding experience. Choose which type of Koha installation you are, fill in a few extra details, and a bunch of settings will get decided for you. Then you can adjust settings as needed, rather than entering into the Administration module and not knowing where to go first. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 16291] New: koha-remove --purge should also delete /etc/koha/sites/instance
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16291 Bug ID: 16291 Summary: koha-remove --purge should also delete /etc/koha/sites/instance Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org It would be useful if 'koha-remove --purge' also deleted a /etc/koha/sites/instance dir -- You are receiving this mail because: You are watching all bug changes.

1 15