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

[Bug 23685] New: Exporting report may consume unlimited memory
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '25

23 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23685 Bug ID: 23685 Summary: Exporting report may consume unlimited memory Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul(a)flo.org QA Contact: testopia(a)bugs.koha-community.org In guided_reports.pl, when exporting report results ($phase eq 'Export') all rows of data are fetched and then converted to the desired format. This may consume an unlimited amount of memory; when report results are particularly large, it may consume all available memory, leading to timed-out HTTP requests, crashes, and potentially data loss. (We have experienced Zebra index corruption as a result.) In master, reports/guided_reports.pl supports three export types -- tab-delimited, CSV, or *.ods. In each case, all data are loaded into memory and held there before any output is produced: 891 $sql = get_prepped_report( $sql, \@param_names, \@sql_params ); 892 my ($sth, $q_errors) = execute_query($sql); ... 895 if ($format eq 'tab') { 896 $type = 'application/octet-stream'; 897 $content .= join("\t", header_cell_values($sth)) . "\n"; 898 $content = Encode::decode('UTF-8', $content); 899 while (my $row = $sth->fetchrow_arrayref()) { 900 $content .= join("\t", @$row) . "\n"; 901 } 902 } else { 903 my $delimiter = C4::Context->preference('delimiter') || ','; 904 if ( $format eq 'csv' ) { ... 914 while (my $row = $sth->fetchrow_arrayref()) { 915 if ($csv->combine(@$row)) { 916 $content .= $csv->string() . "\n"; 917 } else { 918 push @$q_errors, { combine => $csv->error_diag() } ; 919 } 920 } 921 } 922 elsif ( $format eq 'ods' ) { ... 932 # Other line in Unicode 933 my $sql_rows = $sth->fetchall_arrayref(); 934 foreach my $sql_row ( @$sql_rows ) { 935 my @content_row; 936 foreach my $sql_cell ( @$sql_row ) { 937 push @content_row, Encode::encode( 'UTF8', $sql_cell ); 938 } 939 push @$ods_content, \@content_row; 940 } 941 942 # Process 943 generate_ods($ods_filepath, $ods_content); 944 945 # Output 946 binmode(STDOUT); 947 open $ods_fh, '<', $ods_filepath; 948 $content .= $_ while <$ods_fh>; 949 unlink $ods_filepath; 950 } The *.ods case is particularly problematic, because before any data is sent back to the user's browser, *three* copies of the full results are sitting in memory simultaneously -- @$sql_row, @$ods_content, and $content. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 78

[Bug 30819] New: Not able to adjust size of barcode numbers
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '25

23 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30819 Bug ID: 30819 Summary: Not able to adjust size of barcode numbers Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Moved from the original bug 10762: (In reply to Jesse Maseto from comment #0) > I created a new layout (section 2.5.3.1 in the manual) that just shows the > barcode, and I set the font size big. First I did 14, then 32 just to make > sure my eyes weren't deceiving me. The numbers below the barcode didn't > change size! > > It seems like the font settings only affect the bibliographic data. What I > want to change is the barcode number itself. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 30156] New: asterisk is needed before and after barcode
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '25

23 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30156 Bug ID: 30156 Summary: asterisk is needed before and after barcode Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: bugzilla(a)mediapipe.de QA Contact: testopia(a)bugs.koha-community.org Created attachment 131026 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=131026&action=e… Asterisk added before and after barcode An asterisk is needed before and after barcode to show Code39 barcode correctly. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 34732] New: Barcode image generator doesn't generate correct Barcode
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '25

23 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34732 Bug ID: 34732 Summary: Barcode image generator doesn't generate correct Barcode Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kfurst(a)prbschools.org QA Contact: testopia(a)bugs.koha-community.org Created attachment 155281 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=155281&action=e… Code39 Examples When using the barcode generator tool in Koha with the code39 settings, the barcode image it generates is not a code39 barcode and thus can't be read by our book scanners at checkout desks. I'm not sure what type of barcode it is but the generated image does not have the telltale opening and closing lines of a code39. I've attached two screenshots. The first is from the Koha tool with the non-working barcode. The second is from another barcode generating tool that makes a barcode exactly the same as the one on the book I have (already in the catalog). The number it is using is 34517100048832 We're new to Koha so this has been happening since we started using it this summer. Expected behavior would be for it to generate the correct barcode image for a code39 barcode. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 36260] New: Port default PROBLEM_REPORT notice to Template Toolkit syntax
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '25

22 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36260 Bug ID: 36260 Summary: Port default PROBLEM_REPORT notice to Template Toolkit syntax Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: roadmap_24_05 Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Blocks: 15278 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15278 [Bug 15278] [Omnibus] Port default slips and notices from bespoke syntax to Template Toolkit -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 28952] New: Item Checkout History fails
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '25

22 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28952 Bug ID: 28952 Summary: Item Checkout History fails Change sponsored?: --- Product: Koha Version: 21.05 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: beardst(a)rlasd.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 124504 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=124504&action=e… MySQL output We are getting an error whenever trying to view an item's checkout history. This is happening on all items that we have tested /cgi-bin/koha/circ/bookcount.pl?&biblionumber=33518&itm=18222 Results in a 500 error The Plack error log reports CGI::Compile::ROOT::usr_share_koha_intranet_cgi_2dbin_circ_bookcount_2epl::issuessince(): DBI Exception: DBD::mysql::st execute failed: Incorrect TIMESTAMP value: '0' [for Statement "SELECT SUM(count) FROM ( SELECT COUNT(*) AS count FROM issues WHERE itemnumber = ? and timestamp > ? UNION ALL SELECT COUNT(*) AS count FROM old_issues WHERE itemnumber = ? and timestamp > ? ) tmp" with ParamValues: 0="18222", 1=0, 2="18222", 3=0] at /usr/share/koha/intranet/cgi-bin/circ/bookcount.pl line 63 If I run the above sql statement with the variables populated it returns information. Screenshot is attached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 33452] New: Patron statistics results is missing page-section
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '25

22 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33452 Bug ID: 33452 Summary: Patron statistics results is missing page-section 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The patron statistics report is missing the page section on the results table. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 39129] New: Add a notification for staff when a new ILL request is made
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '25

21 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39129 Bug ID: 39129 Summary: Add a notification for staff when a new ILL request is made Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com We don't have a notification for staff when a new ill request is made. It could be useful, and we have that kind of notification when a suggestion is made -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 36596] New: Opening/closing hours should be forced to be set together
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '25

21 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36596 Bug ID: 36596 Summary: Opening/closing hours should be forced to be set together Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 It only seems to make sense to set a closing hour if an opening hour has been set, otherwise it would be open 24 hs :-D A method needs to be added to Koha::Library: * set_hours( $dow, $opening, $closing ) * The method needs to throw an exception if one of them is not passed * If none is passed then it means the library would not be open, and then all hours for the * The code for setting the hours in branches.pl should be removed and this method used instead * The method MUST BE COVERED BY TESTS NOTE: I don't personally like the chosen column name 'day'. I would use either 'dow' or 'day_of_week'. And it should be clear which one is the first in the comments. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 39962] New: Recalled status does not show properly on staff interface record detail page
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '25

21 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39962 Bug ID: 39962 Summary: Recalled status does not show properly on staff interface record detail page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation 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.m.hall(a)gmail.com To reproduce: 1. Enable the UseRecalls system preference and set the recalls-related circulation and fines rules. 2. Search for an item. 3. Check out an item to Patron B. 4. Log into the OPAC as Patron A. 5. Request a record-level recall on the record. 6. View the record on the staff interface and look at the holdings table. Notice that the checked out item shows no indication of being recalled, but the recall request does show on the Recalls tab. --> BUG 7. Go to the Recalls tab and cancel the recall. 8. Go back to the OPAC and request an item-level recall on the checked out item. 9. View the record on the staff interface and look at the holdings table. Notice that the checked out item now shows the recalled status, twice. "Recalled by koha (42) on DATE" --> BUG -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15