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

[Bug 38523] New: Simple quote in ILL standard form JS can break translations
by bugzilla-daemon＠bugs.koha-community.org 03 Jul '26

03 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38523 Bug ID: 38523 Summary: Simple quote in ILL standard form JS can break translations Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com Follow-up of Bug 36221. In Koha/ILL/Backend/shared-includes/shared.js '" name="custom_key" placeholder="'+__('key')+'">' + ' ' + '<input type="text" id="custom-value" name="custom_value" class="' + ( opac ? 'form-control input-fluid custom-field-input' : '') +'" placeholder="'+__('value')+'"> ' + '<button type="button" class="btn btn-danger btn-sm ' + 'delete-new-field">' + '<span class="fa fa-trash-can"></span> ' + __('Delete') + [...] $('#custom-warning').text(__("The name '%s' is not permitted").format(val)).show(); ------- This will need to be tested once bug 38340 has patches. For now stuff is not translatable but once it is, it's expected the JS can break if the translated string contains a simple quote. ------- xt/single_quotes.t doesn't catch it because the test only searches in koha-tmpl/opac-tmpl/bootstrap/en/ koha-tmpl/intranet-tmpl/prog/en/ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 36063] New: Add Holds to Pull info to intranet-main page
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36063 Bug ID: 36063 Summary: Add Holds to Pull info to intranet-main page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We often use JS to add a display to the intranet-main page when there are holds to pull. It would be nice to just add that into Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 44

[Bug 21453] New: blinddetail-biblio-search.pl/.tt use hardcoded subfield values for MARC21
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21453 Bug ID: 21453 Summary: blinddetail-biblio-search.pl/.tt use hardcoded subfield values for MARC21 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: arouss1980(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org If you add or alter an authority record and edit one of the MARC fields in UNIMARC 5XX 'See Also Reference Tracing Block' [1], you can click on the ellipsis (...) next to a subfield [2] to launch the authority finder plugin. This plugin allows you to search for an authority and then pick an entry from the 'Special relationship:' dropdown menu in order to set the relationship between the two authorities. The results list of the authority finder contains 'Choose' buttons which _should_ insert all data from the chosen authority into the appropriate subfields of the MARC tag you are editing [3]. However, in UNIMARC setups this does not work: clicking on 'Choose' only populates subfield $a ('Entry Element') with data, but not subfields $3 and $5 ('Authority Record Number' and 'Tracing Control', respectively), which are just as important for correct authority linking. I've tracked this down to these lines of code which are MARC21-specific and use hardcoded subfield values in blinddetail-biblio-search.pl: 91 for ( $field->subfields ) { 92 next if $_->[0] eq '9'; # $9 will be set with authid value 101 push( @subfield_loop, { marc_subfield => 'w', marc_values => $relationship } ) if ( $relationship ); There is also this code in the template blinddetail-biblio-search.tt: 38 [%- END -%]‡9[% authid | html %]"; 138 if(code.value=='9'){ 139 subfield.value = "[% authid |replace("'", "\'") |replace('"', '\"') |replace('\n', '\\n') |replace('\r', '\\r') %]"; These code fragments don't work 100% because in UNIMARC authorities the authid value is stored in subfield $3 and the relationship code in $5. I propose to modify the Perl script above (which is currently MARC flavour agnostic), have it check the 'marcflavour' system preference, and use that to decide which subfield to push the authority relator code to. A similar approach in the template file will set the authid subfield value depending on whether you are a MARC21 or UNIMARC user. [1] Known as the 'Related Access Point Block' in recent IFLA updates. [2] For the ellipsis to appear next to a subfield, you must view the MARC structure of the relevant authority type and then edit the subfields of the tag you're interested in. Finally, you must select an authority type from the 'Thesaurus:' dropdown menu. [3] Under the hood each 'Choose' button is a call to the JS function doauth(), which in turn calls blinddetail-biblio-search.pl with the parameters required (authid, relationship, etc.). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 36073] New: Add Holds Queue info to intranet-main page
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36073 Bug ID: 36073 Summary: Add Holds Queue info to intranet-main page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Like Bug 36063 but for Holds Queue. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 30849] New: Make pending patron modification notices on staff main page number of modifications at logged in branch
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30849 Bug ID: 30849 Summary: Make pending patron modification notices on staff main page number of modifications at logged in branch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com On the staff main page pending suggestions show some like: Suggestions pending approval: Centerville: 2 / All libraries: 100 It would be nice if we could do the same thing with pending patron modifications Patrons requesting modifications: Centerville: 2 / All libraries: 100 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 42914] New: Default restriction is sometime hardcoded to MANUAL
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42914 Bug ID: 42914 Summary: Default restriction is sometime hardcoded to MANUAL Initiative type: --- Sponsorship --- status: 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(a)bywatersolutions.com Target Milestone: --- Steps to reproduce : 1 - Set the syspref PatronRestrictionTypes to allow 2 - In Adminitration -> PatronRestrictionType, create a new restriction type, make it default 3 - Delete the 'MANUAL' restriction 4 - Go to Tools -> Batch Patron Modifications and add a cardnumber (on ktd 42) 5 - Add a restriction expiration date 6 - Watch Koha burning -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 39429] New: Patron name, branch, and transaction data leak through "Checkout history" when using Library Groups
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39429 Bug ID: 39429 Summary: Patron name, branch, and transaction data leak through "Checkout history" when using Library Groups Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Someone with access to the catalogue can view "Checkout history" which shows transactional information along with the patron's name and branch, even when restrictions are added by Library Groups. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 42897] New: FilterSearchResultsByLoggedInBranch display should expand and collapse
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42897 Bug ID: 42897 Summary: FilterSearchResultsByLoggedInBranch display should expand and collapse Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: kkrueger(a)cuyahogalibrary.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- With the new system preference FilterSearchResultsByLoggedInBranch, it would be nice to be able to expand and collapse the view of all holdings at all locations without needing to keep toggling between show items in all libraries and show local items only. When defaulting to show items in all libraries, a popular title with many copies or a magazine like People with many issues and copies can take up most of the screen of search results. Having an expand/collapse display of holdings across the system per bib record in the results would be ideal. For example, A court of thorns and roses large print edition has 2 copies available at the logged in branch, which show in the location column. There are 27 other copies, which show when clicking on an expand button for that bib in the search results. Clicking the button again collapses the results back to the two at the logged in branch. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 42505] New: Hold transfer slip popup blocked by browser after 'Print slip and confirm' is clicked on hold-found modal
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42505 Bug ID: 42505 Summary: Hold transfer slip popup blocked by browser after 'Print slip and confirm' is clicked on hold-found modal Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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, kyle(a)bywatersolutions.com When returning an item required to fulfil a hold at another branch, with HoldsAutoFill set to 'Don't', the 'Hold found' modal (returns.tt: hold-found-modal / hold-found2 in older versions) is displayed and the librarian must choose 'Confirm hold and transfer' or 'Print slip, transfer, and confirm'. If the librarian clicks the print variant, the slip is opened via window.open() (Dopop()) called from $(document).ready on the page that loads *after* the form submission to confirm the hold. Because the window.open() call happens during a fresh page load, it is not associated with a user gesture, and modern browsers block it as an unsolicited popup. This affects the same code path used for HoldsAutoFill + HoldsAutoFillPrintSlip: the slip popup is fired on document.ready of the response page, with the same popup-blocker risk. Steps to reproduce ================== 1. Set HoldsAutoFill = Don't. 2. Place a hold for a patron with a pickup branch different from the staff member's logged-in branch. 3. Check in the item at the staff member's branch. 4. The 'Hold found' modal appears. 5. Click 'Print slip, transfer, and confirm'. Expected: the hold is confirmed and the hold transfer slip opens in a new window. Actual: the form submits and the hold is confirmed, but the slip popup is blocked by the browser. The librarian sees no slip and may not realise the slip was attempted. Root cause ========== In koha-tmpl/intranet-tmpl/prog/en/modules/circ/returns.tt the .print click handler sets a hidden input print_slip=1 and submits the form. The server (circ/returns.pl) sets the print_slip template parameter on the response, and the response page calls Dopop() (window.open) on document.ready. That window.open() is not within a user gesture event, so popup blockers reject it. Suggested fix ============= Open the print window synchronously inside the .print click handler, while the user gesture is still active. The reserve_id is already present in the modal form as a hidden input, and hold-transfer-slip.pl needs only the reserve_id; the slip content does not depend on the hold having been moved to Waiting state. The form submit to confirm the hold then proceeds in the main window as before. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 23818] New: Acquisitions receipt created when an item or invoice is received.
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '26

02 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23818 Bug ID: 23818 Summary: Acquisitions receipt created when an item or invoice is received. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: rkuiper(a)roundrocktexas.gov QA Contact: testopia(a)bugs.koha-community.org Add a button on each acquisitions invoice that will print a receipt slip fr each item on the invoice. The slip would contain basic information about the item such as title, author and ISBN (to match item to slip) and then other information such as number of holds, branch for multi-branch systems, nonpublic note (we indicate things like NYTimes Best Seller here), and receipt date. Currently we scan the items when they come in and write things like holds and best seller on a slip of paper with the month of receipt on it. I have attached photos of the slips I have seen to give you an idea of what they contain. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12