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

[Bug 7376] Transfer limits should be checked at check-in
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '26

04 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7376 Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #191724|0 |1 is obsolete| | --- Comment #192 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> --- Created attachment 192433 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=192433&action=e… Bug 7376: (follow-up) Extend test coverage and document I'm not sure about the requirements for this bug. This patch extends the tests to cover the new combinations introduced and highlights exactly what changes in the logic.. which appears to be fairly little. Signed-off-by: Julian Maurice <julian.maurice(a)biblibre.com> Signed-off-by: Baptiste Wojtkowski <baptiste.wojtkowski(a)biblibre.com> Signed-off-by: Mathieu Saby <mathsabypro(a)gmail.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7376] Transfer limits should be checked at check-in
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '26

04 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7376 Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #191723|0 |1 is obsolete| | --- Comment #191 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> --- Created attachment 192432 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=192432&action=e… Bug 7376: Unit test Signed-off-by: Julian Maurice <julian.maurice(a)biblibre.com> Signed-off-by: Baptiste Wojtkowski <baptiste.wojtkowski(a)biblibre.com> Signed-off-by: Mathieu Saby <mathsabypro(a)gmail.com> Rebased-by: Victor Grousset/tuxayo <victor(a)tuxayo.net> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7376] Transfer limits should be checked at check-in
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '26

04 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7376 Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #191722|0 |1 is obsolete| | --- Comment #190 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> --- Created attachment 192431 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=192431&action=e… Bug 7376: Transfer limits should be checked at check-in Test case: * UseBranchTransferLimits must be set * define your branch transfer limit. Refuse transfers from libraryA to libraryB * checkout a book owned by libraryB, from libraryB, with a librarian located at libraryB * move the librarian to libraryA ("Set Library" link top/right) * check-in the book => it's possible whatever your setup After the patch, the behaviour respect the branch transfer limit parameter: you can check-in if you accept transfers, you can't if you refuse them. (Note: IndependantBranches must be OFF, otherwise it's not possible to do the checkin whatever the branch transfer limits) TEST PLAN: Note: older signoffs did not validate this test plan Considering you use a ktd-like database. Log in at centerville Allow transfers between centerville, Midway and Franklin, don't allow transfers between Fairfield, Liberty and all other libraries. In addition, allow the transfer between Liberty and Midway Transfer as much books as you can from Centerville to Midway. Log in as Midway, check out as many books from Centerville as you can to Henry Acevedo. If you don't have enough books during the test plan, feel free to check out books again. During the whole test, without further precision, items checkout out in such conditions should be checked in. You will also need 6 checked out floating books at midway Note: '-> ok' means the checkin is allowed '-> not ok' means the checkin is not allowed Apply patch I - Test AllowReturnToBranch During this part of the test plan, you want to have all following configuration : 'CircControlReturnsBranch' -> 'The library the item is checked in at' In CIRC rules: 'Default holds policy and return policy' -> 'Item returns home' (make sure you have no other holds policy on any library) 'AllowReturnToBranch' -> as follows 1 - Set to "Either at the library the item is from or at the library the item was checked out from" X a - Check in to Centerville -> ok X b - Check in to Midway -> ok X c - Check in to Franklin -> not ok X d - Check in to Fairfield -> not ok 2 - Set to "Only at the library the item was checked out from" X a - Check in to Centerville -> not ok X b - Check in to Midway -> ok X c - Check in to Franklin -> not ok X d - Check in to Fairfield -> not ok 3 - Set to "Only at the library the item is from" X a - Check in to Centerville -> ok X b - Check in to Midway -> not ok X c - Check in to Franklin -> not ok X d - Check in to Fairfield -> not ok 4 - Set to "Any library" X a - Check in to Centerville -> ok X b - Check in to Midway -> ok X c - Check in to Franklin -> ok X d - Check in to Fairfield -> not ok II - Transfer and check out 6 floating items at midway. 1 - X a - Check in to Centerville -> ok X b - Check in to Midway -> ok X c - Check in to Franklin -> ok X d - Check in to Fairfield -> ok 2 - Set 'AllowReturnToBranch' to 'home library' X a - Check in to Centerville -> ok X b - Check in to Midway -> not ok III - Pathological & asymetrical cases. During this part of the test plan, you want to have all following configuration : 'CircControlReturnsBranch' -> 'The library the item is checked in at' 'Default holds policy and return policy' -> 'Item returns home' (make sure you have no other holds policy on any library) 'AllowReturnToBranch' -> 'Any library' FOR THIS PART OF THE TESTS ONLY (until IV): Don't allow tranfers from midway to centerville, but allow from centerville to midway X 1 - Check in a book at midway -> not ok Set 'Default holds policy and return policy' -> 'Item returns to issuing library' X 2 - Check in a book at centerville -> ok FOR THIS PART OF THE TESTS ONLY (until IV): Don't allow tranfers from centerville to midway X 3 - Check in a book at centerville -> not ok X 4 - Set 'AllowReturnToBranch' to "Only at the library the item was checked out from" X a - check in to Centerville -> not ok X b - check in to Midway -> not ok IV - Test 'CircControlReturnsBranch' (remove the precedent transfer restriction) During this part of the test plan, you want to have all following configuration : 'Default holds policy and return policy' -> 'Item returns home' (unchanged) 'Default checkout, hold and return policy for Midway' -> 'Item returns to issuing library' 'Default checkout, hold and return policy for Franklin' -> 'Item floats' 'Default checkout, hold and return policy for Fairfield' -> 'Item returns to issuing library' 'Default checkout, hold and return policy for Liberty' -> 'Item returns home' 'AllowReturnToBranch' -> "Any library" (unchanged) 'CircControlReturnsBranch' -> as follows 1 - 'The library the item is checked in at' X a - Check in to Centerville -> ok X b - Check in to Midway -> ok X c - Check in to Franklin -> ok X d - Check in to Fairfield -> not ok X e - Check in to Liberty -> not ok 2 - 'The library the current item is held by X a - Check in to Centerville -> ok X b - Check in to Midway -> ok X c - Check in to Franklin -> ok X d - Check in to Fairfield -> not ok X e - Check in to Liberty -> ok 3 - 'the library the item is owned by' X a - Check in to Centerville -> ok X b - Check in to Midway -> ok X c - Check in to Franklin -> ok X d - Check in to Fairfield -> not ok X e - Check in to Liberty -> not ok Sponsored-by: National Library of Finland Signed-off-by: Arthur Suzuki <arthur.suzuki(a)biblibre.com> Signed-off-by: Julian Maurice <julian.maurice(a)biblibre.com> Signed-off-by: Baptiste Wojtkowski <baptiste.wojtkowski(a)biblibre.com> Signed-off-by: Mathieu Saby <mathsabypro(a)gmail.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 37060] New: KOCT cannot send circulation data due to missing csrf token
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '26

04 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37060 Bug ID: 37060 Summary: KOCT cannot send circulation data due to missing csrf token Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bibliothek(a)th-wildau.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Just tried using the firefox offline circulation tool (koct) and ran into these console errors: ==> /var/log/koha/kohadev/plack-intranet-error.log <== [2024/06/10 11:55:12] [WARN] Programming error - No CSRF token passed for POST http://localhost:8081/intranet/offline_circ/service.pl (referer: No referer) at /kohadevbox/koha/Koha/Middleware/CSRF.pm line 82. To reproduce: a) install firefox addon linked in http://localhost:8081/cgi-bin/koha/circ/circulation-home.pl b) in the plugin settings: server: http://localhost:8081 Login: koha Password: koha c) test login d) check logs for [WARN] Programming error - No CSRF token passed for POST http://localhost:8081/intranet/offline_circ/service.pl (referer: No referer) at /kohadevbox/koha/Koha/Middleware/CSRF.pm line 82. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 62

[Bug 39461] New: Cite feature
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39461 Bug ID: 39461 Summary: Cite feature Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Style guide Assignee: oleonard(a)myacpl.org Reporter: lrudikoff(a)massbay.edu QA Contact: martin.renvoize(a)openfifth.co.uk I have a lot of issues with the Cite feature in KOHA (the Cite in Zotero is fine). Personally, I don't like it as it is not correct at all! For example, the entire title of the item is not listed, there is no complete name of the author, and there is no italicizing for citation styles that use it. It also doesn't list which Chicago style it is using. Why is there both a Cite and Cite in Zotero? As a user, I would not scroll down to see the Cite in Zotero and just use the Cite feature which is listed first. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 8179] Receiving multiple order lines at once
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8179 Monique <monique.prive(a)vsc.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|monique.prive(a)vsc.edu | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 22436] New: add move or copy control field from or to subfield in MARC modification templates
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22436 Bug ID: 22436 Summary: add move or copy control field from or to subfield in MARC modification templates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- MARC modification templates does not allow to mix control field and the subfield of a regular field, we should allow that. But of course not the mix of an entire regular field and the subfield of a regular field. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 38757] New: Adding order from a staged file - "Some required subfields are unset"
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38757 Bug ID: 38757 Summary: Adding order from a staged file - "Some required subfields are unset" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org When ordering from a staged file that contains item data, we have the option to edit or confirm the individual items on the "Select to import" tab, or import all items with identical information from the "Item information" tab. When importing individualized item data from the "Select to import" tab, clicking Save triggers an error: "Some required subfields are unset". Setting the Koha item type in the "Item information" tab fixes this error - but it shouldn't be necessary to set the item type in that tab if all items in the "Select to import" tab already have an item type specified. To replicate: 1. Go to Acquisitions and find or open a basket 2. Click Add to basket 3. Click Add from new file 4. Upload a MARC file containing item data 5. When the upload completes, click "Add to basket" 6. In the "Select to import" tab that comes up by default, check the checkbox next to one or more titles in the file --> This will expand the item data for those titles 7. Look over the item data, and confirm that all items have a homebranch, holdingbranch, and item type defined 8. Click "Save" --> An error pops up: "Some required subfields are unset" 9. Navigate to the "Item information" tab 10. Select a value for y - Koha item type 11. Click "Save" again --> The orders are imported successfully -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 40869] New: Preserve mandatory fields even if hidden when duplicating item
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40869 Bug ID: 40869 Summary: Preserve mandatory fields even if hidden when duplicating item Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When item fields are mandatory, which usually indicate they are somehow critical for functionality and expected to exist in Koha, it makes sense they should be preserved when duplicating an item, even if the field is hidden. Right now hidden fields are ignored using the "ignore_invisible_subfields" option in the form builder for item. If for current library (holding branch) is hidden (which is the case for our library), the biblio page will crash after duplicating an item, which now has a missing holding branch. Fixing this is simple by adding a check for the mandatory attribute in the check for "ignore_invisible_subfields" (I also renamed this option to "ignore_non_mandatory_invisible_subfields" for clarity. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 40860] New: ILL get_notice does not consider HTML template notices
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '26

03 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40860 Bug ID: 40860 Summary: ILL get_notice does not consider HTML template notices Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com ill_full_metadata => $metastring has the attributes joined by a "\n". This does not work if the notice is an HTML notice. For HTML notice, a '<br>' needs to be used instead. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5