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

[Bug 39620] New: Price not populating from 020$c when creating a basket
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39620 Bug ID: 39620 Summary: Price not populating from 020$c when creating a basket Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Have a MRC file with price populated in the 020$c 2. Have nothing the MarcFieldsToOrder or MarcItemFieldsToOrder sys prefs 3. Create a new basket and import from a new file 4. The price is not imported. My understanding is that if the price is set in the 020$c it should be copied over. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 39991] New: Side By Side Record Comparision in Vendor File - Results No Longer Side by Side
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39991 Bug ID: 39991 Summary: Side By Side Record Comparision in Vendor File - Results No Longer Side by Side Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: brian.pichman(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In the past the current record in Koha and the vendor record would be displayed side by side for comparison. Since the latest upgrade, they are now stacked, with the existing Koha record on top, and the vendor record below it. This means for every record we need to check, we have to scroll down to be sure the grid has been applied correctly. Steps to Reproduce The Problem: Receive a .mrc file from a library Stage and upload it through the cataloging module. In order to make sure the grid has been applied on the vendor side, view the record after staging the file. The results are now stacked. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 39534] New: Saved report subgroup filter not hidden correctly
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39534 Bug ID: 39534 Summary: Saved report subgroup filter not hidden correctly Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org When viewing a tab on the saved reports page, a "subgroups" dropdown appears whether or not there are any subgroups for that group. The dropdown should be hidden if there are no subgroups. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 39955] New: Report subgroup filter not cleared when changing tabs
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39955 Bug ID: 39955 Summary: Report subgroup filter not cleared when changing tabs Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org There is an error in the way saved SQL report subgroups behave when you change tabs: The subgroup filter gets applied to the new tab too. Since subgroup codes are unique, this means the all the reports under the tab you switched to are filtered out. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 38847] New: Renewing a child without guarantor whith ChildNeedsGuarantor results in an internal server error
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38847 Bug ID: 38847 Summary: Renewing a child without guarantor whith ChildNeedsGuarantor results in an internal server error Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reproduce: 1 - Create a child, make sure it has no guarantor 2 - Set ChildNeedsGuarantor to Yes 3 - Renew the child -> you will have an internal server error -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 38649] New: Searching for a patron from additem.pl triggers an issue slip to print
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38649 Bug ID: 38649 Summary: Searching for a patron from additem.pl triggers an issue slip to print 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: blawlor(a)clamsnet.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 37407 fixed automatic checkout of items that were fast cataloged from the circulation module. To reproduce: 1. From anywhere on the additem.pl page where you are adding or editing an item 2. Click on Checkout in the menu bar and enter a patron's barcode 3. When circulation.pl loads it triggers a blank issue slip to be printed In addition to checking the referrer for the URL domain and path we should also check the query string of the referrer to make sure it was from a circulation fast add. It should include frameworkcode=FA&circborrowernumber -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 38657] New: Previewing cover images from OPAC search results - image obscured by the search results menu bar
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38657 Bug ID: 38657 Summary: Previewing cover images from OPAC search results - image obscured by the search results menu bar Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org With cover images enabled, if you click on the cover image in the OPAC search results, the image preview is partially hidden behind the search results menu bar. This may depend a little on the size of the image uploaded or returned from the cover image service. To replicate: 1. Enable LocalCoverImages and OPACLocalCoverImages system preferences. 2. Add a cover image to a record. 3. In the OPAC: 3.1 Do a search that will return the record with the cover image in the search results 3.2 Click on the cover image in the search results list 3.3 Note that the image is partially obscured behind the search results menu bar. -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 38701] New: Fix HTML validity errors in invoice template
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38701 Bug ID: 38701 Summary: Fix HTML validity errors in invoice template Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org The invoice template ( Acquisitions -> Invoices -> Invoice details ) has some markup errors which should be fixed. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 39920] New: do_check_for_previous_checkout should us 'IN' over 'OR'
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39920 Bug ID: 39920 Summary: do_check_for_previous_checkout should us 'IN' over 'OR' Change sponsored?: --- Product: Koha Version: Main 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When forming the query for previous checkout we have: 876 # Create (old)issues search criteria 877 my $criteria = { 878 borrowernumber => $self->borrowernumber, 879 itemnumber => \@item_nos, 880 }; This forms a query like: SELECT COUNT( * ) FROM `issues` `me` WHERE ( ( `borrowernumber` = ? AND ( `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? OR `itemnumber` = ? ) ) ): If we instead do: itemnumber => { -in => \@item_nos } We get a query like: SELECT COUNT( * ) FROM `issues` `me` WHERE ( ( `borrowernumber` = ? AND `itemnumber` IN ( ?, ?, ?, ? ) ) ) I believe in the past we fond that MySQL has optimizations for IN and it shortens the query in logs -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 40042] New: search_indexes.inc may have undefined index var
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40042 Bug ID: 40042 Summary: search_indexes.inc may have undefined index var 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: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In koha-tmpl/intranet-tmpl/prog/en/includes/search_indexes.inc some calls do not set 'index' var generating idx="idx_". Set 0 has default value. -- You are receiving this mail because: You are watching all bug changes.

1 18