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

[Bug 34976] New: Encryption keys should not be shared between modules
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34976 Bug ID: 34976 Summary: Encryption keys should not be shared between modules Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org At this time we are using the encryption key in koha-conf to encrypt stuff for 2FA, EDI and Acquisition already. The key was introduced for 2FA. I think that it would be better to differentiate and use separate keys for various processes in Koha. For instance, the key for 2FA should be used exclusively for that purpose. We could consider if that is needed also for EDI and Acq since these are related modules. They could use one or two new keys. When adding a new call to Encryption, we should think about it. Perhaps this would be forced a bit more by passing a parameter to K::E indicating which key to use? Opening the discussion :) What do you think? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 36884] New: Make it possible to use the record_source as a criteria for a search
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36884 Bug ID: 36884 Summary: Make it possible to use the record_source as a criteria for a search Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I'm not sure what would be the more efficient, using SQL and the ORM or add some ES index, but we need to have a way to find all records which belongs to a record_source. It would as well be nice to be able to do a batch edit to change the source of a record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 42197] New: Item search results : display in the filters only values from the results
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42197 Bug ID: 42197 Summary: Item search results : display in the filters only values from the results Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: laurence.rault(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In item search results, dropdown are displayed at the top of the colums to be able to filter the results. However, all the existing values (authorised values, itemtypes, branches) are displayed here, with sometimes very long lists (of locations for example). It would be better if only values existing in the results were proposed in the dropdown. Add also a value "Empty", to be able to display only the results with empty or null values for the column. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 38779] New: Record sources not working on packages install
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38779 Bug ID: 38779 Summary: Record sources not working on packages install Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Interestingly, we miss `record_sources.js` in Makefile.PL Seen this on a packages install: [2024/12/23 10:26:39] [WARN] File not found : js/vue/dist/admin/record_sources.js at /usr/share/koha/lib/Koha/Template/Plugin/Asset.pm line 84. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 32609] New: Remove compiled files from src
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32609 Bug ID: 32609 Summary: Remove compiled files from src Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We need to improve our yarn build commands to generate css and js compiled files. Then remove them from our codebase, and generate them when needed: - when generating the debian packages - when ktd is starting up - when patches are applied on the sandbox -- You are receiving this mail because: You are watching all bug changes.

1 104

[Bug 42485] New: Elasticsearch dynamic mapping date detection causes indexing failures with ARRAY MARC format
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42485 Bug ID: 42485 Summary: Elasticsearch dynamic mapping date detection causes indexing failures with ARRAY MARC format Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major 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 When ElasticsearchMARCFormat is set to ARRAY, the marc_data_array field is configured with dynamic:true in field_config.yaml. Elasticsearch auto-detects field types based on the first document indexed. If a MARC subfield value looks like a date (e.g. '2024-01-15' in 952$e/booksellerid), ES permanently locks that subfield's mapping to type 'date'. All subsequent records with non-date values in the same subfield fail to index with a document_parsing_exception. This affects any subfield stored in marc_data_array that is not explicitly mapped in Koha's search field configuration â most notably item subfields like 952$e (acquisition source), 952$d (date of acquisition), and 952$w (replacement price date). The same issue applies to numeric detection: if the first value for a subfield looks numeric, ES maps it as 'long', and subsequent text values fail. **Root cause** field_config.yaml configures marc_data_array as: marc_data_array: type: object dynamic: true There is no date_detection or numeric_detection control, so ES uses its default behavior of guessing types from values. **Steps to reproduce** 1. Launch a fresh KTD: $ ktd --search-engine es8 --name broken-es --proxy up -d $ ktd --name broken-es --wait-ready 180 2. Get a shell: $ ktd --name broken-es --shell 3. Set ARRAY format, flush cache, wipe records, reset index: k$ koha-mysql kohadev -e "UPDATE systempreferences SET value='ARRAY' WHERE variable='ElasticsearchMARCFormat';" k$ echo 'flush_all' | nc -q1 memcached 11211 k$ koha-mysql kohadev -e "DELETE FROM biblio_metadata; DELETE FROM items; DELETE FROM biblioitems; DELETE FROM biblio;" k$ koha-shell kohadev -c 'rebuild_elasticsearch.pl -d -r --biblios' 4. Add a record with a date-like value in 952$e (booksellerid): k$ koha-shell kohadev -p -c 'perl -MC4::Biblio -MMARC::Record -MMARC::Field -MKoha::Item -e " my \$r = MARC::Record->new(); \$r->append_fields( MARC::Field->new(q{245}, q{1}, q{0}, a => q{Record one}), MARC::Field->new(q{942}, q{ }, q{ }, c => q{BK}), ); my (\$bn) = C4::Biblio::AddBiblio(\$r, q{}); Koha::Item->new({ biblionumber => \$bn, biblioitemnumber => \$bn, homebranch => q{CPL}, holdingbranch => q{CPL}, itype => q{BK}, booksellerid => q{2024-01-15}, })->store; print qq{Added biblio \$bn\n}; "' 5. Index it (this poisons the mapping): k$ rebuild_elasticsearch.pl --biblios -bn <biblionumber> 6. Verify ES auto-detected 952$e as type 'date': k$ curl -s 'es:9200/koha_kohadev_biblios/_mapping/field/marc_data_array.fields.952.subfields.e' => {"type":"date"} 7. Add a second record with a non-date value in 952$e: k$ koha-shell kohadev -p -c 'perl -MC4::Biblio -MMARC::Record -MMARC::Field -MKoha::Item -e " my \$r = MARC::Record->new(); \$r->append_fields( MARC::Field->new(q{245}, q{1}, q{0}, a => q{Record two}), MARC::Field->new(q{942}, q{ }, q{ }, c => q{BK}), ); my (\$bn) = C4::Biblio::AddBiblio(\$r, q{}); Koha::Item->new({ biblionumber => \$bn, biblioitemnumber => \$bn, homebranch => q{CPL}, holdingbranch => q{CPL}, itype => q{BK}, booksellerid => q{My Vendor Name}, })->store; print qq{Added biblio \$bn\n}; "' 8. Try to index â THIS FAILS: k$ rebuild_elasticsearch.pl --biblios -bn <biblionumber> -v -v -v => Record #N failed to parse field [marc_data_array.fields.952.subfields.e] of type [date]... 'My Vendor Name' (document_parsing_exception) **Proposed fix** Set date_detection: false and numeric_detection: false at the mapping root level in get_elasticsearch_mappings() in Koha::SearchEngine::Elasticsearch. These are index-level mapping parameters (not per-field), so they cannot be set in field_config.yaml on the marc_data_array object definition. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 42395] New: Missing translations on load_patron_holds_table
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42395 Bug ID: 42395 Summary: Missing translations on load_patron_holds_table Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com The load_patron_holds_table() datatable is missing some translation tags. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 42299] New: OPAC detail page: star ratings has no associated label
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42299 Bug ID: 42299 Summary: OPAC detail page: star ratings has no associated label Initiative type: --- Sponsorship --- status: 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: lucas(a)bywatersolutions.com 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 To recreate: 1. Set OpacStarRatings so it shows on the OPAC detail page 2. Notice star ratings has no associated label element -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 42245] New: Patron search for guarantors is preselecting borrower sort values from the borrower record
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42245 Bug ID: 42245 Summary: Patron search for guarantors is preselecting borrower sort values from the borrower record Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com av-build-dropbox.inc takes a 'default' param When building the patron we are setting this to the value of sort1, then sort2 This seems to remain cached, and when we build the guarantor search the sort2 value is used as the default To recreate: 1 - Define 2 values for 'BSort1' in Administration -> Authorised values 2 - Define 2 values for 'BSort2' in Administration -> Authorised values 3 - Find a borrower who is eligible to have a guarantor 4 - Edit patron and assign values to sort 1 and 2 for this borrower and save 5 - Edit patron again and click 'Add guarantor' 6 - Note that sort 2 is populated -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 42234] New: OPAC checkout history page table header contains no text
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42234 Bug ID: 42234 Summary: OPAC checkout history page table header contains no text Initiative type: --- Sponsorship --- status: 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: lucas(a)bywatersolutions.com 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 To recreate: 1. Have a user with checkouts 2. Log into the OPAC and go to "Checkout history". 3. In the checkout history table, the first <th> contains no text. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15