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

[Bug 34663] New: Unimarc Default framework
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34663 Bug ID: 34663 Summary: Unimarc Default framework Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org New install Koha 23.05.02 Please correct in the Unimarc Default framework. subfields not in same tabs Not all subfields for the following tags are in the same tab (or marked 'ignored'). Code Description Tag Tabs in use Default framework 410 3,4 Default framework 411 3,4 Default framework 412 3,4 Default framework 413 3,4 Default framework 421 3,4 Default framework 422 3,4 Default framework 423 3,4 Default framework 424 3,4 Default framework 425 3,4 Default framework 430 3,4 Default framework 431 3,4 Default framework 432 3,4 Default framework 433 3,4 Default framework 434 3,4 Default framework 435 3,4 Default framework 436 3,4 Default framework 437 3,4 Default framework 440 3,4 Default framework 441 3,4 Default framework 442 3,4 Default framework 443 3,4 Default framework 444 3,4 Default framework 445 3,4 Default framework 446 3,4 Default framework 447 3,4 Default framework 448 3,4 Default framework 451 3,4 Default framework 452 3,4 Default framework 453 3,4 Default framework 454 3,4 Default framework 455 3,4 Default framework 456 3,4 Default framework 461 3,4 Default framework 462 3,4 Default framework 463 3,4 Default framework 464 3,4 Default framework 470 3,4 Default framework 481 3,4 Default framework 482 3,4 Default framework 488 3,4 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 36371] New: Patron attributes will not show in brief info if value is 0
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36371 Bug ID: 36371 Summary: Patron attributes will not show in brief info if value is 0 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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, nick(a)bywatersolutions.com A patron attribute will not show in the patron brief information if the value for that attribute is 0. This presents an issue for attributes using the YES_NO authorised value, which stores as 1/0. To recreate: 1 - create a patron attribute: check "display in patron's brief info" and tie to the YES_NO authorised value 2 - Find a patron, set your attribute to Yes 3 - Confirm you see the attribute and its value both in the "Additional attributes and identifiers" section of the patron detail page and in the patron brief info area 4 - Set your attribute to No 5 - Confirm you see the attribute and its value in "Additional attributes and identifiers" but it no longer shows in the brief info 6 - Edit your YES_NO authorised value so the codes are Y for Yes and N for No 7 - Find a new patron, repeat steps 2-5, confirm that your No value does show in brief info when the code is N rather than 0 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 35943] New: SQL reports groups/subgroups whose name contains regexp special characters break table filtering
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35943 Bug ID: 35943 Summary: SQL reports groups/subgroups whose name contains regexp special characters break table filtering Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Reports Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Groups and subgroups filtering uses regular expressions. The filter looks like "^" + name + "$" The problem is that the special characters in group/subgroup name are not properly escaped, which means that if a name contains "+", "*", or any other regexp special characters, filtering will probably fail. Another (minor) problem is that we use the name to filter instead of the code. So if we have two groups or two subgroups with the same name, it will show reports from both groups/subgroups. There is no reason to have groups/subgroups with the same name, but it is possible (whereas it's not possible to have different groups/subgroups with the same code), so this should be fixed too. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 35921] New: Improve perfs of acqui-home.pl when there are many budgets
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35921 Bug ID: 35921 Summary: Improve perfs of acqui-home.pl when there are many budgets Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When there are a lot of budgets with the same owner, most of the time of acqui-home.pl is spent loading the same patron over and over. -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 36012] New: ERM/Agreements_spec.ts is failing if run too slow (?)
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36012 Bug ID: 36012 Summary: ERM/Agreements_spec.ts is failing if run too slow (?) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org koha_1 | Running: ERM/Agreements_spec.ts (3 of 13) es_1 | {"type": "server", "timestamp": "2024-02-06T16:59:14,821Z", "level": "WARN", "component": "o.e.c.r.a.DiskThresholdMonitor", "cluster.name": "docker-cluster", "node.name": "9c98971d8b48", "message": "high disk watermark [90%] exceeded on [ZlMDdHYSRcqipOaGsczI_w][9c98971d8b48][/usr/share/elasticsearch/data/nodes/0] free: 2.3gb[5.9%], shards will be relocated away from this node; currently relocating away shards totalling [0] bytes; the node is expected to continue to exceed the high disk watermark when these relocations are complete", "cluster.uuid": "wwW7XQ57T-SNI8QrMEYbPA", "node.id": "ZlMDdHYSRcqipOaGsczI_w" } koha_1 | <?xml version="1.0" encoding="UTF-8"?> koha_1 | <testsuites name="Mocha Tests" time="67.080" tests="5" failures="1"> koha_1 | <testsuite name="Root Suite" timestamp="2024-02-06T16:59:06" tests="0" file="t/cypress/integration/ERM/Agreements_spec.ts" time="0.000" failures="0"> koha_1 | </testsuite> koha_1 | <testsuite name="Agreement CRUD operations" timestamp="2024-02-06T16:59:06" tests="5" time="67.047" failures="1"> koha_1 | <testcase name="Agreement CRUD operations List agreements" time="0.000" classname="List agreements"> koha_1 | <failure message="Timed out retrying after 5000ms: `cy.wait()` timed out waiting `5000ms` for the 4th request to the route: `getActiveAgreements`. No request ever occurred. koha_1 | koha_1 | https://on.cypress.io/wait" type="CypressError"><![CDATA[CypressError: Timed out retrying after 5000ms: `cy.wait()` timed out waiting `5000ms` for the 4th request to the route: `getActiveAgreements`. No request ever occurred. koha_1 | koha_1 | https://on.cypress.io/wait koha_1 | at cypressErr (http://localhost:8081/__cypress/runner/cypress_runner.js:75187:18) koha_1 | at Object.errByPath (http://localhost:8081/__cypress/runner/cypress_runner.js:75242:10) koha_1 | at checkForXhr (http://localhost:8081/__cypress/runner/cypress_runner.js:134821:84) koha_1 | at <unknown> (http://localhost:8081/__cypress/runner/cypress_runner.js:134844:28) koha_1 | at tryCatcher (http://localhost:8081/__cypress/runner/cypress_runner.js:1807:23) koha_1 | at Promise.attempt.Promise.try (http://localhost:8081/__cypress/runner/cypress_runner.js:4315:29) koha_1 | at whenStable (http://localhost:8081/__cypress/runner/cypress_runner.js:143192:68) koha_1 | at <unknown> (http://localhost:8081/__cypress/runner/cypress_runner.js:143133:14) koha_1 | at tryCatcher (http://localhost:8081/__cypress/runner/cypress_runner.js:1807:23) koha_1 | at Promise._settlePromiseFromHandler (http://localhost:8081/__cypress/runner/cypress_runner.js:1519:31) koha_1 | at Promise._settlePromise (http://localhost:8081/__cypress/runner/cypress_runner.js:1576:18) koha_1 | at Promise._settlePromise0 (http://localhost:8081/__cypress/runner/cypress_runner.js:1621:10) koha_1 | at Promise._settlePromises (http://localhost:8081/__cypress/runner/cypress_runner.js:1701:18) koha_1 | at Promise._fulfill (http://localhost:8081/__cypress/runner/cypress_runner.js:1645:18) koha_1 | at <unknown> (http://localhost:8081/__cypress/runner/cypress_runner.js:5450:46) koha_1 | From Your Spec Code: koha_1 | at Context.eval (webpack://koha/./t/cypress/integration/ERM/Agreements_spec.ts:119:11)]]></failure> koha_1 | </testcase> koha_1 | <testcase name="Agreement CRUD operations Add agreement" time="30.510" classname="Add agreement"> koha_1 | </testcase> koha_1 | <testcase name="Agreement CRUD operations Edit agreement" time="6.377" classname="Edit agreement"> koha_1 | </testcase> koha_1 | <testcase name="Agreement CRUD operations Show agreement" time="4.285" classname="Show agreement"> koha_1 | </testcase> koha_1 | <testcase name="Agreement CRUD operations Delete agreement" time="8.038" classname="Delete agreement"> koha_1 | </testcase> koha_1 | </testsuite> koha_1 | </testsuites> I do not recreate locally, is it because we need to extend the timeout? -- You are receiving this mail because: You are watching all bug changes.

1 56

[Bug 29522] New: Bib record not correctly updated when merging identical authorities with LinkerModule set to First Match
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29522 Bug ID: 29522 Summary: Bib record not correctly updated when merging identical authorities with LinkerModule set to First Match Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: 1 - have LinkerModule set to First Match 2 - have a bib with its author linked to an authority 3 - duplicate that authority, confirm that an authority search for your author brings up two identical authorities, one linked to your bib 4 - merge the two authority records, telling Koha to keep the newer of the two (the one not linked to your bib) 5 - search authorities for your author again, confirm you see just one authority and it's not linked to any bibs 6 - reload your bib, see the 100$9 contains the number for the authority you deleted in the merge 7 - edit your bib to correctly link it to the remaining authority 8 - set LinkerModule to Default 9 - repeat steps 3 and 4 10 - see your remaining authority is linked to your bib, the bib has the correct authority number I'm not able to replicate this in master. I'm not sure what changed from 21.05. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 36329] New: Transfer limits should respect `BranchTransferLimitsType`
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36329 Bug ID: 36329 Summary: Transfer limits should respect `BranchTransferLimitsType` Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com CC: tomascohen(a)gmail.com The endpoint allows passing both a `collection code` and an `item type` on a batch request, but the UI would never allow such combination. I wonder if this is a design decision (i.e. supporting both in the future) or just a missing check. My intuition says it is the latter. I'm submitting a patch just in case. Kyle? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 36277] New: t/db_dependent/api/v1/transfer_limits.t is failing
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36277 Bug ID: 36277 Summary: t/db_dependent/api/v1/transfer_limits.t is failing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org This failure is from the last run on master: https://jenkins.koha-community.org/job/Koha_Master/ koha_1 | # Inactivity timeout koha_1 | koha_1 | # Failed test 'POST //qBiciZO7stgLDtFSpp1ZivUHaHyn8cMP1d5DXRI:thePassword123@/api/v1/transfer_limits/batch' koha_1 | # at t/db_dependent/api/v1/transfer_limits.t line 210. koha_1 | koha_1 | # Failed test 'SWAGGER3.2.1' koha_1 | # at t/db_dependent/api/v1/transfer_limits.t line 210. koha_1 | # got: undef koha_1 | # expected: '201' koha_1 | # Looks like you failed 2 tests of 26. koha_1 | koha_1 | # Failed test 'batch_add() and batch_delete() tests' koha_1 | # at t/db_dependent/api/v1/transfer_limits.t line 269. koha_1 | # Looks like you failed 1 test of 4. -- You are receiving this mail because: You are watching all bug changes.

1 39

[Bug 36066] New: REST API: We should not allow deleting open order lines
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36066 Bug ID: 36066 Summary: REST API: We should not allow deleting open order lines Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl CC: tomascohen(a)gmail.com See also bug 10869 and bug 18360. Until now we focused on not deleting order lines in the interface entirely. So it is quite strange that we allow it without any checks on the REST API. In harmony with 18360 we should check if the status is cancelled. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 36103] New: "Cancel hold" link broken for item level holds
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36103 Bug ID: 36103 Summary: "Cancel hold" link broken for item level holds Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lasse.pouru(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com 1. Open the "Holds" tab of a record with an item level hold. 2. Select a patron from the patron search. 3. Click on the "Cancel hold" link. (Link appears as it should, e.g. "modrequest.pl?CancelBiblioNumber=58&CancelBorrowerNumber=5&CancelItemnumber=125"). 4. Popup appears. Click "Confirm cancellation". 5. Page loads. Instead of the correct data for the hold to cancel, all of the values in the URL are null, i.e. "request.pl?action=cancel&borrowernumber=undefined&biblionumber=undefined&reserve_id=undefined". The hold is not cancelled. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24