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

[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 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

[Bug 39962] New: Recalled status does not show properly on staff interface record detail page
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39962 Bug ID: 39962 Summary: Recalled status does not show properly on staff interface record detail page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com To reproduce: 1. Enable the UseRecalls system preference and set the recalls-related circulation and fines rules. 2. Search for an item. 3. Check out an item to Patron B. 4. Log into the OPAC as Patron A. 5. Request a record-level recall on the record. 6. View the record on the staff interface and look at the holdings table. Notice that the checked out item shows no indication of being recalled, but the recall request does show on the Recalls tab. --> BUG 7. Go to the Recalls tab and cancel the recall. 8. Go back to the OPAC and request an item-level recall on the checked out item. 9. View the record on the staff interface and look at the holdings table. Notice that the checked out item now shows the recalled status, twice. "Recalled by koha (42) on DATE" --> BUG -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 33350] New: Show items info several times in notice content
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33350 Bug ID: 33350 Summary: Show items info several times in notice content Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: adolfo.rodriguez(a)xercode.es QA Contact: testopia(a)bugs.koha-community.org In Notices such as Overdue notice (ODUE) you may want to show more than once the info of the overdue items. <item>"<<biblio.title>>" by <<biblio.author>>, <<items.itemcallnumber>>, Barcode: <<items.barcode>> Fine: <<items.fine>></item> Some clients may want to have the info in several languages in the same notice, instead of having a different notice for every language. Right now, if you put <item></item> more than once, it doesn't work properly, as the function GetPreparedLetter (C4/Letters.pm) does the following. Example <item>"<<biblio.title>>" by <<biblio.author>>, <<items.itemcallnumber>>, Barcode: <<items.barcode>> Fine: <<items.fine>></item> <item>"<<biblio.title>>" de <<biblio.author>>, <<items.itemcallnumber>>, Código de barras: <<items.barcode>> Sanción: <<items.fine>></item> It picks everything from the first <item> to the last </item> and replaces <<items.>> with their values. "<<biblio.title>>" by <<biblio.author>>, <<items.itemcallnumber>>, Barcode: <<items.barcode>> Fine: <<items.fine>></item> <item>"<<biblio.title>>" de <<biblio.author>>, <<items.itemcallnumber>>, Código de barras: <<items.barcode>> Sanción: <<items.fine>> The result is a mess that looks like this: The following item(s) is/are currently overdue: "Sucker punch " by Hamilton, Laurell K., , Barcode: CPL22090005 Fine: $0.00 Los siguientes ejemplares tienen retrasos: "Sucker punch " de Hamilton, Laurell K., , Código de barras: CPL22090005 Multa: $0.00 "Legion of Super-Heroes" by Levitz, Paul, , Barcode: CPL23010002 Fine: $0.00 Los siguientes ejemplares tienen retrasos: "Legion of Super-Heroes" de Levitz, Paul, , Código de barras: CPL23010002 Multa: $0.00 It should pick the content between the first <item> and the first </item>, and then the same with the second pair, the third pair and so on. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 33259] New: Optionally set SameSite attribute of cookie to Strict
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33259 Bug ID: 33259 Summary: Optionally set SameSite attribute of cookie to Strict Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSi… We should offer a system preference so that libraries who'd like to increase their security can set the SameSite attribute of the session cookie to Strict, rather than the default Lax. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 103

[Bug 25586] New: Something wrong with KOHA_HOME
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25586 Bug ID: 25586 Summary: Something wrong with KOHA_HOME Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 34808] New: Batch Patron Modification Tool - Select all / clear all does not select/clear all
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34808 Bug ID: 34808 Summary: Batch Patron Modification Tool - Select all / clear all does not select/clear all Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Open the Batch Patron Modification Tool 2. Insert or open a file with 25+ card numbers or borrower numbers to modify then click on continue. 3. Notice that there are 2 or more pages of entries showing. If you click on clear all, it will only clear entries 1-20 but not anything on the second page (21-...). Similarly if you clear both pages and try to select all, it will only select the entries on the page you are viewing. It would useful if the select all/clear all worked on all entries. Especially for libraries that are modifying hundreds of patrons. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 41407] New: OPAC hold history sorts newest to oldest but hides newest to limit to 50
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41407 Bug ID: 41407 Summary: OPAC hold history sorts newest to oldest but hides newest to limit to 50 Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Sort of hold history on the opac is unintuitive. It seems like if it's sorting newest to oldest, it should show the 50 newest holds, not active holds then oldest->newest holds until 50. To recreate on main: 1. Allow to override holds in system preferences 2. Allow borrowers to see HoldHistory in the OPAC 3. place at least 51 holds for a single patron. 4. Backdate some of the hold dates to past days, set one of them to be newer than the rest. 5. log in as that patron on the OPAC 6. Go to the holds history 7. observe the 50 holds and see that your newest one doesn't show 8. click the link to view all and see your newst one does show. -- You are receiving this mail because: You are watching all bug changes.

1 6