January 2023 - Koha-bugs - lists.koha-community.org

[Bug 25711] New: Add ability to define expiredpickup charge for patron category and item type
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25711 Bug ID: 25711 Summary: Add ability to define expiredpickup charge for patron category and item type Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: minna.kivinen(a)hamk.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com ExpireReservesMaxPickUpDelayCharge allows one charge to be applied to all holds that expire. It would be better to have ability to define this charge in ciculation rules. There can be different charges for different types of materials for different patron categories. Related to this bug report: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18195 Charge for expired holds per patron category -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 167

[Bug 24357] New: Hide checkout box when OverduesBlockCirc is set to Block
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24357 Bug ID: 24357 Summary: Hide checkout box when OverduesBlockCirc is set to Block 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 96861 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=96861&action=ed… patron with overdue items If OverduesBlockCirc is set to Block, the checkout box appears in the user's patron file. We can scan the barcode, but only after the item is scanned there is a message saying the patron cannot check out. If NoIssuesCharge is enabled, and the patron owes more than the amount specified, the check out box does not appear at all. Instead, there is a message saying Cannot check out. I think if OverduesBlockCirc is set to Block, the checkout box should be hidden, with a message Cannot check out Patron has overdue items, etc... See screenshots 1) patron with overdue items 2) warning saying that patron cannot checkout after I've already scanned the item's barcode 3) patron with charges over the amount in NoIssuesCharge -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 30546] New: Initial articles not ignored when sorting by the summary column in the pending_orders table
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30546 Bug ID: 30546 Summary: Initial articles not ignored when sorting by the summary column in the pending_orders table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org Bug 29570 (Unable to sort summary column of pending_orders table on parcel.pl by summary column) added sorting capability back to the summary column for the pending orders table. However, search results do not ignore the articles 'a', 'an' and 'the' when displaying the results. I don't believe it used to be like this and other areas in acquisitions, such as invoices, ignore initial articles when displaying search results. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 15986] New: Add a script for sending hold waiting reminder notices
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15986 Bug ID: 15986 Summary: Add a script for sending hold waiting reminder notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Write a script that will take two parameters: a) Length of time hold has been waiting ( in days ) b) Letter code of notice to be emailed 2) Script will take these two parameters and send the specified notice for each hold a patron has. -- You are receiving this mail because: You are watching all bug changes.

1 121

[Bug 24843] New: Allow batch change of framework
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '26

21 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24843 Bug ID: 24843 Summary: Allow batch change of framework Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Koha should give users some method to change the framework of multiple records at once. Batch record modification cannot currently do this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 20551] New: Add option for including deleted records in export_records.pl
by bugzilla-daemon＠bugs.koha-community.org 19 Jul '26

19 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20551 Bug ID: 20551 Summary: Add option for including deleted records in export_records.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Add an option "--include_deleted" to also include possibly deleted biblios in export. This option can only be used together with --date, and --record-type=biblio. The rational behind this is that use case does not makes much sense (if you are doing a full export, why would you include deleted biblios) and thus some extra complexity can be avoided. Superficially related to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17693, not really quite different as this includes the whole biblio-record (with record status set to "d" in leader) in the regular export, not just biblio ids. This is a requirement for synchronizing with the discovery-system we are currently using for example and imho is a more standard and MARC-compliant way of supporting export of record deletions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 205

[Bug 21123] New: Patron card create doesn't print barcodes with Code39 + Modulo
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '26

18 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21123 Bug ID: 21123 Summary: Patron card create doesn't print barcodes with Code39 + Modulo Change sponsored?: --- Product: Koha Version: master 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 I've tested in 16.11, 17.11 and on master and Code39+Module43 and Code39+Modulo10 are not printing for me, while just Code39 works fine. When exporting, the PDF is not created, instead a yellow error message is shown: WARNING: Error while creating PDF file. Batch: 1 Layout: 22 Template: 26 Please have your system administrator check the error log for details. koha-plack-err does show a lot of those: CGI::param called in list context from package Template::Document line 20, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436. CGI::param called in list context from package Template::Document line 13, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436. CGI::param called in list context from package Template::Document line 14, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436. I've tested with the sample patrons, who have numerical cardnumbers like: Pamela Bennett, 23529000318858 -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 31241] New: PDF export of ANY label is NOT functioning.
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '26

18 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31241 Bug ID: 31241 Summary: PDF export of ANY label is NOT functioning. Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: stdominic.novices(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I've been experimenting and no label type of any kind works when exported as a pdf. Either it is completely jumbled or massive amounts of the data are missing. I've tried batch and selected exporting, redoing the layouts and templates. This is for Patron, barcode, and spine label. I have a similar bug concerning the spine label, but this seems to be a more widespread problem than I first thought. If I try to export a singly selected or any other number that is not the full batch I get an Error 500 message, and if it's the full bath the label is garbled. Thanks for your time looking into this! -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 28297] New: can't save system preference and field not marked as modified when changing value
by bugzilla-daemon＠bugs.koha-community.org 18 Jul '26

18 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28297 Bug ID: 28297 Summary: can't save system preference and field not marked as modified when changing value Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com == Test plan == 1. Search any syspref that has a text input 2. input a value, like 3, you see "modified" 3. save 4. refresh (tech note: the <input> will now have value=3) 5. input 5, you see "modified" 6. save (tech note: the <input> still has value=3, this is the cause) 7. input 3, you don't see "modified" (this in wrong) 8. save 9 "nothing to save", this is wrong -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 28884] New: ElasticSearch: Question mark in title search returns no results
by bugzilla-daemon＠bugs.koha-community.org 17 Jul '26

17 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28884 Bug ID: 28884 Summary: ElasticSearch: Question mark in title search returns no results Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: jyorio(a)equinoxinitiative.org When searching for a title with a question mark, Who's Afraid of Virginia Woolf? for example, Koha returns no results with ElasticSearch. Removing the question mark or escaping it retrieves results, as does enclosing the entire title with the question mark in quotes. Since ? is a wildcard for ElasticSearch, this may be expected behavior (I'm not sure that it is or isn't), but explaining to patrons that they need to change their search behavior can be a big ask for libraries. Not sure what the best option is. Perhaps a system preference to automatically escape ? and not treat it as a wildcard for those libraries who would prefer that? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 60