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

[Bug 38127] New: Missing column headings in 'Add user' pop-up modal
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38127 Bug ID: 38127 Summary: Missing column headings in 'Add user' pop-up modal Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org In the 'Add user' pop-up modal, the column headings in the results are missing. To get there (with ktd data): 1. Go to Acquisitions 2. Click 'Search' to find 'My vendor' 3. Click 'My basket' 4. Click 'Add to basket' 5. Click 'From a new (empty) record' 6. Click 'Add user' 7. Search for 'alford' (for example) --> Note that there aren't any column headings in the results Compare with: 1. Go to Tools > Patron card creator 2. Click 'New' > 'Card batch' 3. Click 'Add patron(s)' 4. Search for 'alford' (for example) --> Note that there are column headings in this pop-up I get that they are different modals (Add user vs Add patrons), but I just wanted to highlight the column headings. I found this while documenting Bug 35329, but I'm not sure if it's related directly to that one. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 34147] New: Patron Search Displays "Processing" when Category Has Library Limitations that Exclude the Logged In Branch Name
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34147 Bug ID: 34147 Summary: Patron Search Displays "Processing" when Category Has Library Limitations that Exclude the Logged In Branch Name Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: jyorio(a)equinoxinitiative.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I'll start by saying that I don't know if this relates to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24132 or not. To replicate, you'll need more than one library in Administration | Libraries. Setup a patron category with a Library Limitation, so that one library is excluded (by not selecting it). Create a patron with a common surname in your borrowers table and assign to that category. While the logged in branch is set to one of the libraries that are not excluded for that category you created above, search for patrons with the surname of your test patron. You should get results as expected. Change the logged in branch name to the excluded library. Conduct the same search. A processing message appears and just spins. I'm not sure whether the desired result should be to exclude the patron in question from the search results or whether it should display but with some restriction on the Patron Category. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 38101] New: ES skips records with huge fields
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38101 Bug ID: 38101 Summary: ES skips records with huge fields Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I saw a case in the wild, where the staff member copied and pasted some legal text from a PDF into a 500 field. Then the record was not able to be found using ES. The reason is fairly simple: ES has a max size it will accept for a phrase index. To reproduce: 1. Have KTD running with ES: $ ktd --proxy --es7 up -d 2. Perform a search 3. Pick the first result for edition 4. Find a cool Wiki page with lots of paragraphs 5. Copy all of the paragraphs and put them on a 500$a field for the record. 6. Repeat 2 => FAIL: The record is not found 7. Reindex manually: $ ktd --shell k$ perl misc/search_tools/rebuild_elasticsearch.pl --biblios --where "biblionumber=3" -v -v => FAIL: You get something like: ``` [22229] Committing final records... One or more ElasticSearch errors occurred when indexing documents at /kohadevbox/koha/Koha/SearchEngine/Elasticsearch/Indexer.pm line 148. [22229] There were errors during indexing Record #3 Document contains at least one immense term in field="note.raw" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms. The prefix of the first immense term is: '[10, 109, 117, 115, 116, 97, 102, 97, 32, 102, 117, 101, 32, 101, 108, 32, 115, 101, 103, 117, 110, 100, 111, 32, 104, 105, 106, 111, 32, 100]...', original message: bytes can be at most 32766 in length; got 32771 (illegal_argument_exception) : max_bytes_length_exceeded_exception (bytes can be at most 32766 in length; got 32771) [22229] Total 1 records indexed ``` -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[Bug 38422] New: Add data-isbn and data-title to lists for plugin cover images
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38422 Bug ID: 38422 Summary: Add data-isbn and data-title to lists for plugin cover images Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It isn't possible to display plugin cover images on the OPAC lists view - we need to enable the plugin method and pass the item data to the element -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 38367] New: offset is wrong on plugins-disabled.tt page
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38367 Bug ID: 38367 Summary: offset is wrong on plugins-disabled.tt page 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: 1. Go to your koha-conf.xml and turn plugins off: <enable_plugins>0</enable_plugins> 2. Go to Administration -> Plugins 3. The text is not correctly offset. ( Bootstrap class is col-sm-offset-3 and should be offset-sm-3 in Bootstrap 5 ) ` -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 38350] New: Fix style of sidebar form clear buttons
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38350 Bug ID: 38350 Summary: Fix style of sidebar form clear buttons Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Keywords: Academy Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org In cases where sidebar forms have a submit button alongside a clear button, the submit button is supposed to be larger than the clear button. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 13722] Titles with articles not sorting correctly in lists
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13722 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au --- Comment #12 from David Cook <dcook(a)prosentient.com.au> --- Is this still an issue? The alphabetic title ascending sort in http://localhost:8080/cgi-bin/koha/opac-shelves.pl?op=view&shelfnumber=1 is working for me with a title starting with the indefinite article "A ". The staff interface sorting is just totally non-functional at the moment... bug 40312 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 40486] New: Item type not handled correctly when placing holds in staff interface
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40486 Bug ID: 40486 Summary: Item type not handled correctly when placing holds in staff interface Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com When using the system preference "AllowHoldItemTypeSelection", you can specify the item type you want for "next available" holds. Unfortunately, on /cgi-bin/koha/reserve/request.pl there is a "Request specific item type:" field at the top under "Hold details" and another under "Hold next available item". Both of these fields get sent, which means that only the 1st one works. (To reproduce, enable that system preference and try to set the item type using the "Request specific item type:" under "Hold next available item". On the hold screen, "Books" won't appear in the "Details" column. Try again using the top field and this time you'll see under "Details" it says "Next available <itemtype> item".) Also, it looks like this "itemtype" isn't passed to CanBookBeReserved. It just goes straight to AddReserve(). (See bug 40475 for more detail.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 40475] New: Item type not considered for next available hold in OPAC
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40475 Bug ID: 40475 Summary: Item type not considered for next available hold in OPAC Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com I was discussing CanBookBeReserved with Pedro on bug 15516 when I noticed that the $itemtype in the following line of opac/opac-reserve.pl looks like it'll always be "undef" for "next available" holds: my $status = CanBookBeReserved( $borrowernumber, $biblioNum, $branch, { itemtype => $itemtype } )->{status}; -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 32135] New: Ability to batch cancel transfers
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '25

23 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32135 Bug ID: 32135 Summary: Ability to batch cancel transfers Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: madamyk(a)ckls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com For consortiums and other large systems, it would be helpful to have the ability to batch cancel transfers, or cancel more than one at a time. Most likely the easiest place to do this would be on the Transfers to Receive page, where you might be able to add a "Cancel Transfer" checkbox instead of (or in addition to) the button. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7