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

[Bug 39490] New: Web Usability Accessibility Audit - Table Columns Missing Headings
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '25

25 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39490 Bug ID: 39490 Summary: Web Usability Accessibility Audit - Table Columns Missing Headings Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Accessibility Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexander.blanchard(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, oleonard(a)myacpl.org The Web Usability Accessibility Audit has highlighted that in the 'My Account' section, some of the tables are missing descriptive column headers so the data / functionality of these columns may not be clear. The suggested solution is to populate these columns with text that accurately describes the content / functionality users will find in the columns. A side effect of this will be that the text size in the columns may be reduced. Are there any thoughts on this? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 38179] New: koha-common runtime dependency on yarn
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38179 Bug ID: 38179 Summary: koha-common runtime dependency on yarn Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org On main as of bug 37303, for 24.11 onwards, in order to run: ```shell koha-translate --install <LANG> ``` Both `yarn` and `po2json` are required. A recollection of information about it: * Debian's version of node-po2json is not what we want: bug 37303 comment 21 => we don't want to be stuck with v0.4.5 * Yarn version might not be an issue * Node.js version could be an issue This change got reverted on 24.05.x (bug 38164) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 34200] New: Lists and merge catalog records
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34200 Bug ID: 34200 Summary: Lists and merge catalog records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: klas.blomberg(a)skovde.se QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Merge merge two catalogue records that are added to different lists. The resulting merged record will be included only in the list of the master record, and not in the list of the deleted record. The same thing applies also when the master record is not included in any list, but the deleted record were in a list. In that case the merged record will not be included in any list -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 23794] New: Convert OpacMainUserBlock system preference to news block
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23794 Bug ID: 23794 Summary: Convert OpacMainUserBlock system preference to news block Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: hayleymapley(a)catalyst.net.nz, jonathan.druart(a)bugs.koha-community.org, katrin.fischer(a)bsz-bw.de, lucas(a)bywatersolutions.com, m.de.rooy(a)rijksmuseum.nl, testopia(a)bugs.koha-community.org Depends on: 22318 Building on 22318, the OpacMainUserBlock system preference should be converted to a Koha news block. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22318 [Bug 22318] Extend Koha news feature to include other content areas -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 38082] New: Advanced editor does not save the selected framework
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38082 Bug ID: 38082 Summary: Advanced editor does not save the selected framework Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P3 Component: Cataloging Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When creating a fresh record in the advanced editor, it does not save the framework selected from the Settings dropdown. -- You are receiving this mail because: You are watching all bug changes.

1 27

[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