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

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

14 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 22

[Bug 43808] New: LocalHoldsPriority follows Transport cost matrix rather than position in queue
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43808 Bug ID: 43808 Summary: LocalHoldsPriority follows Transport cost matrix rather than position in queue Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: klas.blomberg(a)skovde.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Target Milestone: --- Set LocalHoldsPriority to Give library, then library group Create a local hold group with at least three libraries - the more libraries the better for this test Set UseTransportCostMatrix to Use Enter some values in the Transport cost matrix for the libraries in the hold group Place holds for a title to pick-up on each one of the libraries in the group. Check-in the item at it’s home branch and it fills the hold for the patron on that branch – as expected. Return the item from the first borrower. As there are no more borrowers waiting for the item at the home branch we expect it to go to the first borrower in queue at some other branch in the hold group. Instead it goes to the borrower at the branch with lowest value in the Transport cost matrix, irrespective of what position that borrower has in the queue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 41240] New: Add configurable hold skip limit to LocalHoldsPriority
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41240 Bug ID: 41240 Summary: Add configurable hold skip limit to LocalHoldsPriority Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com A new configuration option allows the admin to set the maximum number of times a hold can be skipped. Once this limit is reached, the hold must be prioritized and filled. Improves fairness in hold fulfillment and prevents holds from being ignored due to prioritization. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 41095] New: Allow to limit LocalHoldsPriority filling to a maximum number of holds in the queue
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41095 Bug ID: 41095 Summary: Allow to limit LocalHoldsPriority filling to a maximum number of holds in the queue Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Libraries want to limit the LocalHoldsPriority filling to match only x number of holds in the queue. If there are 100 holds and they want to allow the LocalHoldsPriority system preference to check only 20 first holds for example. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 39989] New: Expand LocalHoldsPriority groups to allow different settings by group
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39989 Bug ID: 39989 Summary: Expand LocalHoldsPriority groups to allow different settings by group Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some libraries would like to be able to set LocalHoldsPriority to be able to have each group set to Group vs Library and Group instead of the same for all groups. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 39118] New: Make facet labels translatable
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39118 Bug ID: 39118 Summary: Make facet labels translatable Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Bug 35138 made adding or modifying facets much easier. However, and it was pointed out at the start of the bug report, user-created facets (or user-modified facets) aren't translatable. It would be great if we could have a way of translating them (without using the JS hack). To recreate: 1. Make sure your installation is using ElasticSearch (if using ktd, do `ktd --es7 up` or `ktd --es8 up`) 2. Make sure your installation has at least two languages 2.1. Install new language ktd --shell --root koha-translate --install fr-CA --dev kohadev 2.2. Go to Administration > System preferences 2.3. Search for languages 2.4. Check the new language in OPACLanguages and StaffInterfaceLanguages 2.5. Click 'Save all I18N/L10N preferences' 3. Add a facet (for example, Genre/Form on 655$a in MARC21) 3.1. Go to Administration > Search engine configuration (Elasticsearch) 3.2. In the 'Search fields' tab, find index-term-genre 3.3. Change the label to 'Genre/Form' 3.4. Click 'Save' 3.5. Go to the 'Bibliographic records' tab 3.6. In the last row of the 'Facet order' table, choose 'index-term-genre' 3.7. Click 'Add' 3.8. Click 'Save' 3.9. Go to the 'Bibliographic records' tab again 3.10. Find index-term-genre and change 'Facetable' to 'Yes' 3.11. Click 'Save' 4. Reindex ktd --shell ./misc/search_tools/rebuild_elasticsearch.pl -b -v -d (DO NOT USE -r or all your work in step 3 will be lost :((( ) 5. Search for "comedy" in the staff interface catalog --> The new facet is there with its label "Genre/Form" 6. Switch the interface to the other language 7. Redo step 5 --> The new facet's label is not translated 8. Search for "comedy" in the staff OPAC catalog --> The new facet is there with its label "Genre/Form" 9. Switch the OPAC to the other language 10. Redo step 8 --> The new facet's label is not translated Note: "Hardcoded" facets, such as Authors, Topics, etc. are currently translatable. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 41506] New: Should we remove RabbitMQ?
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41506 Bug ID: 41506 Summary: Should we remove RabbitMQ? 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the hackfest in Wellington this came up as a question in the discussion and it was decided to bring it up at the next development meeting. https://koha-hedgedoc.servers.llownd.net/Development_IRC_meeting_26_Novembe… The discussion is difficult and we want to include as many opinions/people as possible. I felt it would be a bit lost on bug 35920, so proposing a separate bug report instead. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 38

[Bug 43806] New: Add ability to prefork the Z39.50/SRU responder ( z3950_responder.pl ) with a maximum number of children
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43806 Bug ID: 43806 Summary: Add ability to prefork the Z39.50/SRU responder ( z3950_responder.pl ) with a maximum number of children Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- Currently the z3950_responder.pl hands its accept loop to the YAZ frontend server through Net::Z3950::SimpleServer. YAZ forks a new child for every connection and has no limit on how many children it will create. Each child is a full Koha Perl process, so a burst of connections, or a pile of idle sessions held open until the idle timeout ( 60 minutes by default ), can use up all the memory on a server! It would be good to be able to cap concurrent sessions and keep a pool of preforked workers, the same way the SIP server does with Net::Server::PreFork. YAZ can serve a single connection in inetd mode ( -i ) and then return control to Perl, so Net::Server::PreFork can own the listening socket and each child can hand its accepted connection to YAZ. Each child serves one session and then exits. We should add the following options to z3950_responder.pl, settable through z3950_responder_options in the instance's z3950/config.xml: * --max-servers ( enables preforking ) * --min-servers * --min-spare-servers * --max-spare-servers Without --max-servers the responder should behave exactly as it does today. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 43760] New: Add the ability for staff to send pending notice immediately
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43760 Bug ID: 43760 Summary: Add the ability for staff to send pending notice immediately Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: roman.dolny(a)jezuici.pl QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk Target Milestone: --- It would be useful if staff members could immediately send pending notice (listed in Notice tab) to user. It could by done by "Send immediately" button at notice preview. Sometimes a librarian needs to send a (predefined) message to a user they are currently talking with in the library (e.g., message with a specially prepared link). Currently, a predefined message (like many others) is added to the queue and will be sent according to the cron job schedule (usually every 15 minutes). Adding a "Send Immediately" button (similar to the "Resend" button for messages that have already been sent) could be good solution. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 41246] New: Deleting patron categories can leave orphaned rules in the overduerules table
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41246 Bug ID: 41246 Summary: Deleting patron categories can leave orphaned rules in the overduerules table Initiative type: --- Sponsorship --- status: 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com To recreate: 1. Add or have a patron category. 2. Go to Tools > Overdue notice/status triggers 3. Set some rules for that category. 4. Delete the patron category 5. Now do "select distinct categorycode from overduerules;" 6. The rule remains with a non-existent categorycode -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22