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

[Bug 33609] New: Script delete_records_via_leader.pl should work with authority records
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '26

01 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33609 Bug ID: 33609 Summary: Script delete_records_via_leader.pl should work with authority records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently this only works with biblios, we should provide the same service for authorities -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 38630] New: Make the REST API respect KohaOpacLanguage cookie
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '26

01 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38630 Bug ID: 38630 Summary: Make the REST API respect KohaOpacLanguage cookie Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Holidays Assignee: koha-bugs(a)lists.koha-community.org Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 32551 Continuation of bug 32551 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32551 [Bug 32551] API requests don't carry language related information -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 39851] New: Languages for REST API is returned in random order
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '26

01 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39851 Bug ID: 39851 Summary: Languages for REST API is returned in random order Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com At least for the tests: Run t/db_dependent/api/v1/ill_requests.t several times. If you have several languages installed it will fail randomly: # $got->[0]{_strings}{status}{str} = 'Solicitado' # $expected->[0]{_strings}{status}{str} = 'Requested' or # $got->[0]{_strings}{status}{str} = 'Angefordert' # $expected->[0]{_strings}{status}{str} = 'Requested' This is because getlanguage hit the else: if ( $interface eq 'opac' || $interface eq 'intranet' ) { [...] } else { @languages = map { $_->{rfc4646_subtag} } @{ getTranslatedLanguages( $interface, $theme ) }; $language = Koha::Language->get_requested_language(); } and getTranslatedLanguages returns the languages in a random order. So there might be several problems highlighted here. You can easily recreate the problem with: use C4::Languages; use C4::Context; C4::Context->interface('api'); say C4::Languages::getlanguage(); -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 39001] New: Language list is displayed in wrong order (getLanguages doesn't sort it, the order is UB)
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '26

01 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39001 Bug ID: 39001 Summary: Language list is displayed in wrong order (getLanguages doesn't sort it, the order is UB) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: schodkowy.omegi-0r(a)icloud.com QA Contact: testopia(a)bugs.koha-community.org Caught by unit tests added in Bug 38646, but it's not a regression of that bug. It seems that the list of languages from getLanguages is not ordered in any way, instead it relies on the implementation detail of the database server in terms of the order it returns things in. Indeed even before that bug was merged, in Koha 24.11 and 24.05, one can observe in OPAC -> Advanced search -> Language, that the order of languages is indeed a bit wrong (for example: amh, grc, ara -- Old Greek (grk) has nothing starting with "a", so it has no business being this high in the list). The solution in principle is simple, just order the returned language list (TBD what to order it by: by language code, by English name, by effective final display name????). It's also TBD whether getLanguages should sort it itself, or whether places that display languages, such as `/cgi-bin/koha/opac-search.pl`, should actually be doing the ordering in preferred fashion. In any case, the tests at t/db_dependent/Languages.t fail due to wrong order after some MariaDB update, so current order is undefined behavior. Also if we select to change the behavior of getLanguages, then it'll be trickier to backport it, since dependent Bug 38646 is enhancement due to slight change of behavior. But the backporter could easily adjust the SQL query there to make the lines "THEN CONCAT(" be selected with removing the conditional, so that the language list is always appended in parentheses (old behavior). -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 40022] New: Release team 25.11
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '26

01 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40022 Bug ID: 40022 Summary: Release team 25.11 Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org New cycle, new release team. Let's add the new team to the about page. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 34037] New: Item Bundles do not correctly checkin the bundle if the 952$3 has text
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '26

01 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34037 Bug ID: 34037 Summary: Item Bundles do not correctly checkin the bundle if the 952$3 has text Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using the bundled feature, if the item that is getting checked out has a 952$3, the check-in will not be successful. This main item can not have this field, although this field is helpful for staff to know it is a bundle and has items included. Step 1. Create a bundle of items Step 2. The 'main' item in which will be checked out to the patron - make sure it has a 952$3 with text. Step 3 Check out the 'main' item that has the items attached to it. See the materials specified text appear at checkout. Step 4 Checkin in the 'main' item and the subsequent items. Step 5 See that all items are verified Step 6 Koha will bring the staff member back to the screen to do the check-in. Step 7 Go to the 'main' item and see the bundle is still checked out to the patron. Removing the materials specified from the main item, and the check-in will then be successful and be removed from the patron's account. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 40666] New: Item type translations don't work on detail page in staff
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '26

01 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40666 Bug ID: 40666 Summary: Item type translations don't work on detail page in staff Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com, tomascohen(a)gmail.com In 24.11.05 the itemtype translations work well for the detail page in the OPAC, but in the staff interface the itemtype always shows the default description. The description shows correctly in other parts of Koha, so this appears to be related to the API use maybe? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 37900] New: Prevent to search all patrons at once
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '26

01 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37900 Bug ID: 37900 Summary: Prevent to search all patrons at once Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kati.sillgren(a)porvoo.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com members-home.pl There should be a way to prevent searching all patrons at once. For example by requiring a search value in the field 'Search'. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 33675] New: OAuth should support state parameter
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '26

01 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33675 Bug ID: 33675 Summary: OAuth should support state parameter Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Some Authentication solutions require a 'state' parameter to be passed during authentication to verify the sources on either end, it is supported by Mojolicious: https://metacpan.org/pod/Mojolicious::Plugin::OAuth2 We should add this to Koha -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 36762] New: Item not transferred correctly when there is a pending hold
by bugzilla-daemon＠bugs.koha-community.org 31 May '26

31 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36762 Bug ID: 36762 Summary: Item not transferred correctly when there is a pending hold Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Koha is doing some dumb stuff when one attempts to transfer an item that could fill a pending hold. To recreate: 1 - be logged in at Branch A 2 - have a bib with 1 holdable item at Branch A 3 - place a hold for pickup at Branch B 4 - confirm hold shows on Holds to Pull and Holds Queue 5 - go to Circulation > Transfers and attempt to send your item to Branch C 6 - Koha gives you three options. Pick the first one: "Transfer to Branch B." This is the hold pickup branch, not the branch you selected for your transfer 7 - Koha tells you it has transferred the item to Branch C (the branch you did select for your transfer) 8 - go to detail.pl for your title, confirm the holdings table says "there is an item level hold" on your item 9 - click to the Holds tab for your title, confirm the hold claims to be in transit 10 - query the branchtransfers table, confirm no transfer was created 11 - query reserves and confirm your hold has found=T, itemnumber=[your item], and item_level_hold=0 12 - Back on the title, attempt to revert transit status, confirm the Revert button doesn't do anything At step 6, Koha should offer to transfer to the indicated transfer-target, rather than the hold pickup branch. Then it should actually generate the transfer and should not insert the itemnumber into the reserves table or update reserves.found. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27