February 2022 - Koha-bugs - lists.koha-community.org

[Bug 30003] New: When leaving 'Amount Tendered' blank, then filling in a value, two transactions are recorded
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '22

08 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30003 Bug ID: 30003 Summary: When leaving 'Amount Tendered' blank, then filling in a value, two transactions are recorded Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: jake.deery(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org (Possibly related to #28163 at a code level) Hi, One of our customers has raised a curious bug involving the Point of Sale module within Koha. Specifically, when processing a payment in Koha, if the 'amount tendered' field is left blank, then filled in after the 'this field is mandatory' text appears, the transaction seems to be recorded twice. Please see here for a visual demo: https://i.imgur.com/upH5zlk.gifv Steps to reproduce: 1. Navigate to /cgi-bin/koha/pos/pay.pl 2. Add an item from 'items to purchase' 3. Under 'collect payment', click submit without altering the form 4. See 'This field is required.' 5. Now, fill a value in 'Amount tendered' that satisfies or exceeds 'Amount being paid' 6. The payment should succeed 7. Navigate to /cgi-bin/koha/pos/register.pl 8. See duplicate lines in Transactions I hope we can see this resolved quickly, as it has the potential to cause major accounting issues. Many thanks, Jake Deery -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 29576] New: Add streetype to fields which can be copied from guarantor to guarantee
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '22

08 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29576 Bug ID: 29576 Summary: Add streetype to fields which can be copied from guarantor to guarantee Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: didier.gautheron(a)biblibre.com Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 22534 Since #22534 you can prefill addresses but streettype and B_streettype aren't in koha-tmpl/intranet-tmpl/prog/en/modules/admin/preferences/patrons.pref list. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22534 [Bug 22534] Add ability to choose which fields are copied from guarantor to guarantee -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 30114] New: Koha offline circulation will always cancel the next hold when issuing item to a patron
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '22

08 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30114 Bug ID: 30114 Summary: Koha offline circulation will always cancel the next hold when issuing item to a patron 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a record has holds on it, and, using offline circulation, an item on that is checked out to a patron that did not have a hold on the record, the next hold that would have trapped that item will be canceled. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 29501] New: gather_print_notices.pl does not use SMTP servers
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '22

08 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29501 Bug ID: 29501 Summary: gather_print_notices.pl does not use SMTP servers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Bug 22343 added the ability to specify SMTP servers for outgoing email, removing the need to run an MTA (like postfix) on the server. As far as I can tell, gather_print_notices.pl does it's own email sending with MIME::Lite, bypassing the message_queue and the SMTP server setup. So in order to use this as a cronjob to send print as email, you have to run an MTA anyway. Could this be fixed, so the script uses the SMTP server setup? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 30094] New: Rewrite some of the patron searches when requesting an article with the REST API route
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '22

08 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30094 Bug ID: 30094 Summary: Rewrite some of the patron searches when requesting an article with the REST API route Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 23528] New: Show 'log in to add tags' link on all search result entries
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '22

08 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23528 Bug ID: 23528 Summary: Show 'log in to add tags' link on all search result entries Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Splitting this out as a separate bug report from bug 23210: (In reply to Lucas Gass from comment #0) > If a non-authenticated user goes to the search results page they will only > see the login4tags (Log in to add tags ) text included with the first > result. This should be included with every result. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 28264] New: Transaction type is empty is cash register statistics wizard report
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '22

07 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28264 Bug ID: 28264 Summary: Transaction type is empty is cash register statistics wizard report Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Hi all! When I do a report using the statistics wizard, the transaction type doesn't appear. I think maybe this has something to do with the "new" structure for accounttypes which are now separated in credit_type_code and debit_type_code... To test: 1) Go into a patron file and add some manual fees and pay them 2) Go to Reports > Statistics wizards > Cash register 3) In the form, choose Transaction type: All transactions 4) Click "Submit" 5) Note that the Transaction type column is empty 6) In the form, choose Output: To a file 7) Click "Submit" 8) Open the file in a spreadsheet software (I use LibreOffice) 9) The Transaction type column is empty A client reported this to me after we upgraded them from 19.05.04 to 20.05.08. In 20.05 (in the client's db), the Transaction type column is filled when viewing the report in the browser, but when we export the report, it's empty. In my master (default db), the transaction types don't appear in either cases. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 26381] New: Koha should provide Koha plugins with a template to use with Template::Toolkit WRAPPER
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '22

07 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26381 Bug ID: 26381 Summary: Koha should provide Koha plugins with a template to use with Template::Toolkit WRAPPER Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, Koha plugins have to built their own templates from scratch. I'm proposing that Koha provides a BLOCK or a template file that Koha plugins can then use with the Template::Toolkit WRAPPER directive to minimize the amount of boiler plate they have to use. Here is an example of a very simple "plugin_wrapper" [% BLOCK plugin_wrapper %] [% INCLUDE 'doc-head-open.inc' %] <title>Koha: [% name %]</title> [% INCLUDE 'doc-head-close.inc' %] </head> <body> [% INCLUDE 'header.inc' %] [% INCLUDE 'cat-search.inc' %] <div id="breadcrumbs"><a href="/cgi-bin/koha/mainpage.pl">Home</a> &rsaquo; <a href="/cgi-bin/koha/plugins/plugins-home.pl">Plugins</a> &rsaquo; [% breadcrumb %]</div> <div id="doc3"> [% content %] [% INCLUDE 'intranet-bottom.inc' %] [% END %] Then, in my report-step1.tt file, all I need to include is the following: [% WRAPPER plugin_wrapper name = 'My Plugin' breadcrumb = 'My Plugin' %] <div>Plugin content</div> [% END %] I've already tested this a little bit, and it's beautiful. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 23330] New: deleteditemsstocknumberidx should not be a unique index
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '22

07 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23330 Bug ID: 23330 Summary: deleteditemsstocknumberidx should not be a unique index Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, deleteditemsstocknumberidx is a unique index, which means that an item will fail to delete if its "Inventory number" already exists in the deleteditems table. Its counterpart itemsstocknumberidx was renamed to itemstocknumberidx in version 3.03.00.042 (dating from April/May 2011) and made non-unique. I've worked on Koha since early 2012 and only today have I had someone stung by this problem. They've been storing "Copy number" in "Inventory number" for some reason, and it's caught them out. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 28758] New: Undefined subroutines in C4/ImportBatch.pm (bug 17600)
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '22

06 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28758 Bug ID: 28758 Summary: Undefined subroutines in C4/ImportBatch.pm (bug 17600) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12