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

[Bug 31114] New: OpacHiddenItems is not respected in search results when an OPAC search is filtered by branch
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '26

04 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31114 Bug ID: 31114 Summary: OpacHiddenItems is not respected in search results when an OPAC search is filtered by branch Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lucy.vaux-harvey(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org When filtering OPAC searches by library (OpacAddMastheadLibraryPulldown enabled) the search results will include title records where all items for that library are hidden from the OPAC due to the values in OpacHiddenItems. When clicking through to the detailed view of an affected record the copies are correctly hidden in the holdings table but it is confusing for the library customer to find the title in the search results. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 28862] New: Add suffix to name field
by bugzilla-daemon＠bugs.koha-community.org 03 Aug '26

03 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28862 Bug ID: 28862 Summary: Add suffix to name field Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: rcoert(a)arlingtonva.us QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Requesting the addition to the name field for suffix entries (Jr., Sr. III, etc.). Ideally it would be a drop-down box that could be prepopulated (auth_value?) with common entries; allowing for cleaner data and easier account viewing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 29768] New: hidepatronname hides guarantor name on borrower edit screen
by bugzilla-daemon＠bugs.koha-community.org 03 Aug '26

03 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29768 Bug ID: 29768 Summary: hidepatronname hides guarantor name on borrower edit screen Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: bdaeuber(a)cityoffargo.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The syspref hidepatronname is now hiding the guarantor name on memberentry.pl. This seems like a strange place to enforce that system preference since it's convenient for staff to be able to double check that info when editing patron information and personal information is already showing on that screen. It's not enforced on other patron details screens (such as moremember.pl) and I don't think it should impact patron edit screen either. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 53

[Bug 42324] New: Authority auto-created from bib heading truncates trailing dots in $f date for living authors
by bugzilla-daemon＠bugs.koha-community.org 03 Aug '26

03 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42324 Bug ID: 42324 Summary: Authority auto-created from bib heading truncates trailing dots in $f date for living authors Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When a bibliographic record is saved with a personal name heading (example) containing a living author date in $f (e.g. “1970-….”), Koha automatically creates an authority record with a truncated $f value (“1970-…” instead of “1970-….”). One dot is silently dropped. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 41469] New: Convert Traditional Chinese to Simplified Chinese for searching
by bugzilla-daemon＠bugs.koha-community.org 03 Aug '26

03 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41469 Bug ID: 41469 Summary: Convert Traditional Chinese to Simplified Chinese for searching Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We have had a request for supporting the conversion of traditional characters to simplified characters There are elastic tools/analyzers for this: https://github.com/infinilabs/analysis-stconvert https://www.elastic.co/docs/reference/elasticsearch/plugins/analysis-smartcn However, in testing I have not been able to get things working. The requester suggested some config for Zebra as well, but I couldn't get that working either Filing this here to capture conversations I had with David Cook and so he can share the setup he tried ;-) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 40817] New: Holds charges should be accessible from Holds
by bugzilla-daemon＠bugs.koha-community.org 03 Aug '26

03 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40817 Bug ID: 40817 Summary: Holds charges should be accessible from Holds Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com Depends on: 3492 It should be easy to get from a hold to it's associated charges.. i.e. Hold fee, Cancellation fee, any processing fees. This would be useful for API responses and display purposes. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3492 [Bug 3492] Move hold fee setting into circulation rules -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 52

[Bug 18523] New: Filter Circulation lists on home library
by bugzilla-daemon＠bugs.koha-community.org 03 Aug '26

03 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18523 Bug ID: 18523 Summary: Filter Circulation lists on home library Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using IndependentBranches, items of other sites should not be seen in this Circulation lists for staff users (except for superlibrairians) : - Holds awaiting pickup - Pending on-site checkouts -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 41460] New: On Mysql on upgrade from 25.05 to 25.11 I got the error TEXT column 'value' can't have a default value
by bugzilla-daemon＠bugs.koha-community.org 02 Aug '26

02 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41460 Bug ID: 41460 Summary: On Mysql on upgrade from 25.05 to 25.11 I got the error TEXT column 'value' can't have a default value Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: michael.hafen(a)washk12.org QA Contact: testopia(a)bugs.koha-community.org Mysql does not allow blob or text type columns to have a default. The systempreferences.value column is the only occurrence of this I found in the kohastructure.sql file. It seems Mysql will ignore the default null as long as the column allows null, so that's not an issue. Bug 40405 sets systempreferences.value to NOT NULL, but tries to also add a DEFAULT '', which causes Mysql to throw the above error. Proposed solution is to remove the DEFAULT '' part of the clause from the db_rev file. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 37598] New: Ability to use the BCC field for sending notices to multiple addresses, rather than the To field
by bugzilla-daemon＠bugs.koha-community.org 02 Aug '26

02 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37598 Bug ID: 37598 Summary: Ability to use the BCC field for sending notices to multiple addresses, rather than the To field Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Bug 12802 allows libraries to select a list of email address fields to use when sending notices to patrons. You would check all of the email addresses you want to use in a new system preference EmailFieldSelection and Koha will send the notice to all of those addresses. However, all of those addresses do go through in the To field. They are not in the BCC field. It would be good to enable the option to use the BCC field for the email addresses rather than the To field. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 44

[Bug 42174] New: Elasticsearch throws "Too many clauses" error
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '26

01 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42174 Bug ID: 42174 Summary: Elasticsearch throws "Too many clauses" error 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In ES8 or ES9 in KTD if you search with a lot of terms like: is this too many search terms to search a a single time maybe you get in the logs: [http://es:9200]-[400] [illegal_argument_exception] Query rewrite failed: too many clauses, called from sub Search::Elasticsearch::Role::Cxn::process_response at /kohadevbox/koha/Koha/SearchEngine/Elasticsearch.pm line 56. With vars: {'status_code' => 400,'body' => {'status' => 400,'error' => {'type' => 'search_phase_execution_exception','failed_shards' => [{'reason' => {'reason' => 'Query rewrite failed: too many clauses','type' => 'illegal_argument_exception','caused_by' => {'reason' => 'Query contains too many nested clauses; maxClauseCount is set to 1024','type' => 'too_many_nested_clauses'}},'index' => 'koha_kohadev_biblios','node' => 'o6de3CLcQfmF5HA5oW8QsQ','shard' => 0}],'root_cause' => [{'type' => 'illegal_argument_exception','reason' => 'Query rewrite failed: too many clauses'}],'reason' => 'all shards failed','caused_by' => {'caused_by' => {'type' => 'illegal_argument_exception','reason' => 'Query rewrite failed: too many clauses','caused_by' => {'reason' => 'Query contains too many nested clauses; maxClauseCount is set to 1024','type' => 'too_many_nested_clauses'}},'reason' => 'Query rewrite failed: too many clauses','type' => 'illegal_argument_exception'},'grouped' => bless( do{\(my $o = 1)}, 'JSON::PP::Boolean' ),'phase' => 'query'}},'request' => {'method' => 'GET','ignore' => [],'serialize' => 'std','body' => {'query' => {'bool' => {'must' => [{'query_string' => {'lenient' => bless( do{\(my $o = 1)}, 'JSON::PP::Boolean' ),'query' => '(is* this* too* many* search* terms* to* search* a* a* single* time* maybe*)','fuzziness' => 'auto','analyze_wildcard' => $VAR1->{'request'}{'body'}{'query'}{'bool'}{'must'}[0]{'query_string'}{'lenient'},'type' => 'cross_fields','default_operator' => 'AND','fields' => ['music-key','number-local-acquisition','title-collective','date-entered-on-file','ln-audio','stack','author','lf','author-name-corporate','rtype','cn-bib-source','local-number','title-former','datelastseen','name-geographic','datelastborrowed','control-number-identifier','cn-sort','issues','identifier-other','date-time-last-modified','host-item','number-db','materials-specified','biblioitemnumber','issn-all','coden','price','lc-card-number','totalissues','publisher','author-title','geolocation_lon','identifier-publisher-for-music','personal-name','bgf-number','language-original','issn','cn-suffix','lost','author-personal-bibliography','title-other-variant','reserves','musical-presentation','title-expanded','ln','subject-name-personal','uri','ff7-01-02','itemtype','restricted','editor','ff8-29','barcode','itype','llength','lc-call-number','author-in-order','geolocation_lat','material-type','microform-generation','title-uniform','bnb-card-number','record-control-number','nal-call-number','stock-number','curriculum','coded-location-qualifier','code-geographic','identifier-standard','author-name-personal','title-cover','name','code-institution','number-govt-pub','renewals','interest-age-level','homebranch','cross-reference','damaged','acqsource','interest-grade-level','index-term-uncontrolled','ff7-01','extent','index-term-genre','thematic-number','ln-subtitle','itemnumber','bib-level','isbn','copynumber','not-onloan-count','date-of-acquisition','koha-auth-number','title-series','arp','title-later','nlm-call-number','copydate','current-publication-frequency','date-of-publication','classification-source','ctype','title-no-punctuation','name-and-title','map-scale','number-legal-deposit','cn-bib-sort','bio','number-natl-biblio','cn-prefix','withdrawn','related-periodical','dewey-classification','cn-class','ta','holdingbranch','record-source','ff8-23','abstract','ff7-00','cn-item','title','replacementprice','local-classification','corporate-name','report-number','dissertation-information','note','location','other-control-number','control-number','udc-classification','reading-grade-level','notforloan','ccode','su-geo','indexed-by','host-item-number','replacementpricedate','subject','title-key','title-abbreviated','arl','geographic-class','provider','pl','isbn-all','lexile-number','conference-name','ff7-02']}}],'should' => [{'match' => {'title-cover' => {'query' => 'is this too many search terms to search a a single time maybe'}}}]}},'size' => '20','aggregations' => {'itype' => {'terms' => {'field' => 'itype__facet','size' => '20'}},'homebranch' => {'terms' => {'field' => 'homebranch__facet','size' => '20'}},'location' => {'terms' => {'field' => 'location__facet','size' => '20'}},'su-geo' => {'terms' => {'size' => '20','field' => 'su-geo__facet'}},'ccode' => {'terms' => {'size' => '20','field' => 'ccode__facet'}},'author' => {'terms' => {'size' => '20','field' => 'author__facet'}},'title-series' => {'terms' => {'size' => '20','field' => 'title-series__facet'}},'holdingbranch' => {'terms' => {'size' => '20','field' => 'holdingbranch__facet'}},'ln' => {'terms' => {'size' => '20','field' => 'ln__facet'}},'subject' => {'terms' => {'size' => '20','field' => 'subject__facet'}}},'sort' => [{'_score' => {'order' => 'desc'}},{'local-number' => {'order' => 'desc'}}],'from' => 0},'qs' => {'track_total_hits' => 'true'},'path' => '/koha_kohadev_biblios/_search','mime_type' => 'application/json'}} Checking ES documentation it seems both the way clauses are calculated and the limit have changed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2