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

[Bug 30533] New: Add exact search option for patrons
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30533 Bug ID: 30533 Summary: Add exact search option for patrons Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com A patron search for names like "JOHN JOHNSON" ends up getting parsed something like "WHERE surname like "%JOHN%" OR firstname like "%JOHN%" OR surname like "%JOHNSON%" OR firstname like "%JOHNSON%"" and finds a really unhelpfully large pile of patrons. Bug 17500 suggests implementing Elastic for patron searching, which would be great. In the meantime, we could give a little help for searches like this by giving an exact search option -- so the query would parse more or less the same but without the wildcards. That's also a problematic search for many situations, but would work better here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 42026] New: Add fallback label text when ind. 2 is empty for 264
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42026 Bug ID: 42026 Summary: Add fallback label text when ind. 2 is empty for 264 Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: pascal.uphaus(a)gwdg.de Currently, when 264 ind. 2 is left empty, Koha won't show a label for the field in the OPAC. As quality of records might vary, it would be good to add a fallback to the XSLT that covers unknown and empty ind. 2 values. https://git.koha-community.org/Koha-community/Koha/src/commit/e7855c0c016e2… -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 31504] New: ElasticSearch No indexing new records after upgrade
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31504 Bug ID: 31504 Summary: ElasticSearch No indexing new records after upgrade Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: hagud(a)orex.es After upgrading koha 21.11 to 22.05 ElasticSearch is not able to index new records. At webadmin we can see the warning 'Index 'koha_xxxxxx' needs to be recreated.' Executing 'Reset mapping' button doesn't fix the error... when trying to full reindex with option -d or -r it doesn't work admin@___21:~$ sudo koha-elasticsearch --rebuild -d ___ sudo: unable to resolve host ___21: Name or service not known sudo: unable to resolve host ___21: Name or service not known Use of uninitialized value $reason in concatenation (.) or string at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Indexer.pm line 283. Exception 'Koha::Exception' thrown 'Unable to update mappings for index "koha_____biblios". Reason was: "". Index needs to be recreated and reindexed' Something went wrong rebuilding indexes for ___ Removing the index directly at ElasticSearch doesn't works * ElasticSearch is not localhost -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 42025] New: Error handling in tools/upload is broken
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42025 Bug ID: 42025 Summary: Error handling in tools/upload is broken Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 13618 On the following commit we add the html filter to msg: commit dcd1f5d48c758aee17b6c6f069c6146b42efe117 Date: Fri Jan 23 13:18:54 2015 +0100 Bug 13618: Add html filters to all the variables - ShowAlerts( [% msg %] ); + ShowAlerts( [% msg | html %] ); msg is supposed to be a JSON encoded string: tools/upload.pl 118 my $msg = 119 $delete ? JSON::to_json( { $fn => { code => ALERT_DELETED } } ) 120 : $id ? JSON::to_json( { $fn || $id, { code => ERR_NOT_DELETED } } ) 121 : ''; So we could use To.json in the template and remove the to_json from the controller. BUT... There are a couple places in the controller where we send back what we send: 38 my $msg = $input->param('msg'); 76 msg => $msg, Which would lead to XSS if we remove the filtering. This script receives msg in parameter when sent from SubmitMe 462 function SubmitMe(op, id, msg ) { 465 $("#submitter #msg").val( msg ); coming from: 398 function cbUpload( status, fileid, err ) { 399 $('#fileToUpload').prop('disabled', false); 400 if( status=='done' ) { 401 var e = err? JSON.stringify(err): ''; 402 SubmitMe( 'search', fileid, e ); Coming from 364 function StartUpload() { 387 xhr= AjaxUpload( $('#fileToUpload'), $('#fileuploadprogress'), xtra, cbUpload ); Which does...: koha-tmpl/intranet-tmpl/prog/js/file-upload.js 1 function AjaxUpload(input, progressbar, xtra, callback) { 10 var url = "/cgi-bin/koha/tools/upload-file.pl?" + xtra; 19 xhr.onload = function (e) { 20 var data = JSON.parse(xhr.responseText); 21 if (data.status == "done") { 22 progressbar.val(100); 23 progressbar.next(".fileuploadpercent").text("100"); 24 } 25 callback(data.status, data.fileid, data.errors); 26 }; tools/upload-file.pl 55 send_reply( 'failed', undef, $upload ? $upload->err : undef ); 63 sub send_reply { # response will be sent back as JSON 64 my ( $upload_status, $data, $error ) = @_; 65 my $reply = CGI->new(""); 66 print $reply->header( -type => 'text/html', -charset => 'UTF-8' ); 67 print JSON::encode_json( 68 { 69 status => $upload_status, 70 fileid => $data, 71 errors => $error, 72 } 73 ); Koha/Uploader.pm 154 sub err { 155 my ($self) = @_; 156 my $err; 157 foreach my $f ( keys %{ $self->{files} } ) { 158 my $e = $self->{files}->{$f}->{errcode}; 159 $err->{$f}->{code} = $e if $e; 160 } 161 return $err; 162 } All this is VERY messy... Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13618 [Bug 13618] Add additional template filter methods and a filter presence test to Koha -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 13618] Add additional template filter methods and a filter presence test to Koha
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13618 Jonathan Druart <jonathan.druart(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |42025 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42025 [Bug 42025] Error handling in tools/upload is broken -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 41147] New: Counts in bulkmarcimport.pl are incorrect
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41147 Bug ID: 41147 Summary: Counts in bulkmarcimport.pl are incorrect Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz We are incrementing the record_number counter twice for every record -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 38365] Add Content-Security-Policy HTTP header to HTML responses
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '26

08 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38365 --- Comment #324 from David Cook <dcook(a)prosentient.com.au> --- @Lari do you want to do a test of these latest patches and then I can mark SO and Jonathan can look at QA? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38365] Add Content-Security-Policy HTTP header to HTML responses
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '26

08 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38365 --- Comment #323 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Jonathan Druart from comment #321) > Yep, see the last patch ("Add test_valuebuilder_popup.tt to the exception > list"), it's how we add exception to Koha::Devel::Files. Ahhhh that's cool. Awesome! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8937] Translation process removes CDATA in RSS XML
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '26

08 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8937 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42022] New: Add custom patron message broken if notice has library limitation
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '26

08 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42022 Bug ID: 42022 Summary: Add custom patron message broken if notice has library limitation Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com To reproduce: 1. Go to Tools -> Notices and slips 2. Create a new notice, choose 'Patrons (custom message)' from the modules dropdown 3. Change the Library to Centerville and fill in an email notice, then hit Save 4. Go to your patron account and ensure you have a primary email address saved for the patron 5. Go to the Notices tab 6. Click the Add message button in the navbar 7. Change 'Add a message for:' to Email 8. Change 'Patron notice:' to your new custom message template and Save 9. The page should refresh and you'll see that the notice was NOT generated --> BUG The plack-intranet-error.log will also complain that it couldn't find the notice for that transport type, but this is due to the library limitation. If you create another custom message for All libraries, this can be generated and sent as normal. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1