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

[Bug 37201] New: Add a syspref to allow or not a checkout if a expired booking exists for the same patron
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '25

07 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37201 Bug ID: 37201 Summary: Add a syspref to allow or not a checkout if a expired booking exists for the same patron Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hello :) I've worked on a way to prevent checkout to patron if this same patron has a booking expired for the same item.. I think it's a setting that might not suit everyone, so I've introduced a new system preference. I'll put my patch in place and await your comments. Thanks ^^ -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 37885] New: Add ability to disable message queue processing
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '25

07 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37885 Bug ID: 37885 Summary: Add ability to disable message queue processing Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org There exist services that libraries utilize as an alternative to processing the message queue. These services may utilize the queued messages and send them from outside of Koha. Sometimes these services utilize the API or reports while other times they utilize a plugin. It would be beneficial to be able to disable running the message queue processor altogether, or to only execute the plugin hook related to message queue processing ( before_send_messages ) to limit the processing of messages to those handled by plugins. I think a new system preference along the lines of "Process/Don't process/Process only via plugins" would be good, but haven't quite come up with a sentence that makes sense. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 37359] New: Advanced editor should work with unimarc
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '25

07 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37359 Bug ID: 37359 Summary: Advanced editor should work with unimarc Change sponsored?: --- 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: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In the manual I read for EnableAdvancedCatalogingEditor : "This feature does not currently include any support for UNIMARC or NORMARC fixed fields." Is it true? If so, it could be an improvement to make this feature available for UNIMARC installs -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 38720] New: HTML1 no longer valid? TT tags can be present in HTML without breaking the translator tool
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '25

07 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38720 Bug ID: 38720 Summary: HTML1 no longer valid? TT tags can be present in HTML without breaking the translator tool Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We have the following coding guidelines: ``` HTML1: Template Toolkit markup inside HTML Avoid [% IF %] inside tags because the translation tools try to read the templates as straight HTML and most TT comments inside tags probably confuse/break them. The most common example of an incorrect construction: <option value="1" [% IF (selected) %] selected="selected" [% END %]>Yes</option> This must be written this way: [% IF (selected) %] <option value="1" selected="selected">Yes</option> [% ELSE %] <option value="1">Yes</option> [% END %] ``` Everybody (should) know about it, and we are all aware it must not be done like that. But... I will need it for bug 38664 and I have decided to have a look at fixing it. However I have not managed to break anything! I did introduce TT tags within HTML tags, but the strings are correctly picked and the translated templates is perfectly generated. What am I missing here? Did we finally fix this long-standing problem without knowing it? -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 39219] New: Error when issuing a refund from the transaction table
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '25

07 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39219 Bug ID: 39219 Summary: Error when issuing a refund from the transaction table Change sponsored?: --- 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: - Create a manual invoice: $10.00 - Pay using the pay button in the transactions table: $1.00 - Now issuing a refund explodes into: Exception 'Koha::Exceptions::ParameterTooHigh' thrown 'Amount to payout (3.00) is higher than amountoutstanding (0)' at /usr/share/perl5/Exception/Class/Base.pm line 88 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 31507] New: When printing barcode range labels library name does not print
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '25

06 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31507 Bug ID: 31507 Summary: When printing barcode range labels library name does not print Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org With the ability to print barcode labels from a range, using the Home or Holding description data within the label layout, it does not print any info, since by default, these are barcodes that do not have items yet, and therefore, no home or holding data. It would be really helpful to have a way to have the library info appear without having to manually enter the library name in the fields data. This is particularly important for libraries with multiple branches where you don't want to have to change the library name, nor have a lot of different layouts. Perhaps the default for this scenario could be the logged in library if there is no home or holding? -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 37856] New: Some SUSHI providers require the platform parameter
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '25

06 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37856 Bug ID: 37856 Summary: Some SUSHI providers require the platform parameter Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: pedro.amorim(a)ptfs-europe.com Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, michaela.sieber(a)kit.edu, pedro.amorim(a)ptfs-europe.com The harvest_sushi method produces the following URL when harvesting SUSHI data: <provider_url>/reports/<report_type>?customer_id=<customer_id>&requestor_id=<requestor_id>&api_key=<api_key>&begin_date=<begin_date>&end_date=<end_date> Some providers require the 'platform' parameter. Docs here: https://app.swaggerhub.com/apis/COUNTER/counter-sushi_5_0_api/5.0.2#/defaul… We need to look for a way to identify when/if a provider requires this parameter, and add it to the URL if so. The provider in question is ScienceDirect: https://registry.countermetrics.org/platform/ab4d3560-1165-491d-a67e-9359d0… The 'platform parameter required' entry is unchecked even though this provider requires it. We should consider using this to identify if the parameter is required or not. -- You are receiving this mail because: You are watching all bug changes.

1 53

[Bug 39828] New: QuickAdd skips fields from PatronQuickAddFields in some cases
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '25

06 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39828 Bug ID: 39828 Summary: QuickAdd skips fields from PatronQuickAddFields in some cases Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: slavashishkin(a)gmail.com Reporter: slavashishkin(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using PatronQuickAddFields to add fields to the Quick Add form, fields that exist in the main form but contain multiple input elements (especially hidden/disabled ones) may be silently skipped during QuickAdd form generation. Example: "userid" field exists in the full patron form (entryform) as: > <li> > <label for="userid">Username:</label> > <input type="text" id="userid" name="userid" ...> > <input type="text" disabled="disabled" style="display:none" ...> > </li> The current JavaScript logic to detect and clone these fields uses: > let orig_input_id = orig_li.children("input,textarea,select").last().attr("id"); In this example, .last() selects the hidden disabled input without an id → orig_input_id becomes undefined → and the field is not cloned into QuickAdd form. Result: userid is missing from Quick Add even though it's included in PatronQuickAddFields. Steps to reproduce: 1. Add userid (or any other field that matches above structure) to PatronQuickAddFields. 2. Open the Add Patron form and use Quick Add. 3. Observe → the field is missing. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 28492] New: Hyphen in branchcode gives wrong search results
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '25

05 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28492 Bug ID: 28492 Summary: Hyphen in branchcode gives wrong search results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org A client noticed that when limiting by branch, some search results were wrong and after a bit of digging, I found that it happens when the branchcode contains a hyphen. I was able to recreate the situation as follows: 1) Go to Administration > Libraries and add the libraries - Fairfield (branchcode FFL) -- if you have the default database, this library should already exist - Fairfield North (branchcode FFL-N) - Fairfield South (branchcode FFLS) 2) Add an item to record A with holding branch FFL-N 3) Add an item to record B with holding branch FFLS 4) reindex if necessary 5) In Advanced search, search for record A and limit to Fairfield North library -- record is in the results - OK 6) In Advanced search, search for record A and limit to Fairfield library -- record is in the results! - NOT OK 7) In Advanced search, search for record B and limit to Fairfield South library -- record is in the results - OK 8) In Advanced search, search for record B and limit to Fairfield library -- record is not in results - OK As you can see, the search for branchcode FFL-N and for branchcode FFL give the same results. The problem was originally found by a client using 18.05.03. I was able to recreate in 20.05.08 and master (21.06.000), always with Zebra. I didn't try with ES because mine is currently broken :( -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 39243] New: Display Item Group in patron’s list of checked out items
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '25

05 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39243 Bug ID: 39243 Summary: Display Item Group in patron’s list of checked out items Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: rpalermo(a)oslri.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In Koha, when a patron has an item attached to an item group checked out, the item group does not show on their checked out screen. We use item groups for individual periodical issues and it would be helpful to be able to let the patron know which issue they have checked out by looking at that screen. We would like to see Item Group as one of the options when selecting Columns Settings so we could add that to the display. Currently the only way for library staff to tell the patron which periodical issue (item group) they have checked out is to go into bib record, click the normal tab to go to the holdings table, search for barcode to see the item group. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3