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

[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

[Bug 20421] New: Inform staff that patron does have the title checked out during placing hold
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '22

06 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20421 Bug ID: 20421 Summary: Inform staff that patron does have the title checked out during placing hold 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 30155] New: We shouldn't calculate get_items_that_can_fill when we don't have any holds
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '22

05 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30155 Bug ID: 30155 Summary: We shouldn't calculate get_items_that_can_fill when we don't have any holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This breaks the 'Holds to pull' report in 21.05.09 if there are no holds "Fixed" by bug 3142 in 21.05.11 and master The problem is essentially that calculation of @bibs_or_items can be empty if no holds are passed, so our SQL Abstract call ends up with an emptpy -or block, which in turn leads to our where beginning with "AND" DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'AND `itemlost` = '0' AND `itemnumber` NOT IN ( '156269' ) AND 1=1 AND `notforloa' at line 1 [for Statement "SELECT `me`.`itemnumber`, `me`.`biblionumber`, `me`.`biblioitemnumber`, `me`.`barcode`, `me`.`dateaccessioned`, `me`.`booksellerid`, `me`.`homebranch`, `me`.`price`, `me`.`replacementprice`, `me`.`replacementpricedate`, `me`.`datelastborrowed`, `me`.`datelastseen`, `me`.`stack`, `me`.`notforloan`, `me`.`damaged`, `me`.`damaged_on`, `me`.`itemlost`, `me`.`itemlost_on`, `me`.`withdrawn`, `me`.`withdrawn_on`, `me`.`itemcallnumber`, `me`.`coded_location_qualifier`, `me`.`issues`, `me`.`renewals`, `me`.`reserves`, `me`.`restricted`, `me`.`itemnotes`, `me`.`itemnotes_nonpublic`, `me`.`holdingbranch`, `me`.`timestamp`, `me`.`location`, `me`.`permanent_location`, `me`.`onloan`, `me`.`cn_source`, `me`.`cn_sort`, `me`.`ccode`, `me`.`materials`, `me`.`uri`, `me`.`itype`, `me`.`more_subfields_xml`, `me`.`enumchron`, `me`.`copynumber`, `me`.`stocknumber`, `me`.`new_status`, `me`.`exclude_from_local_holds_priority` FROM `items` `me` WHERE ( ( AND `itemlost` = ? AND `itemnumber` NOT IN ( ? ) AND 1=1 AND `notforloan` = ? AND `onloan` IS NULL AND `withdrawn` = ? ) )" with ParamValues: 0=0, 1=156269, 2=0, 3=0] at /usr/share/koha/lib/Koha/Objects.pm line 145 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 28200] New: Net::Netmask 1.9104-2 requires constructor change for backwards compatibility
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '22

05 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28200 Bug ID: 28200 Summary: Net::Netmask 1.9104-2 requires constructor change for backwards compatibility Change sponsored?: --- Product: Koha Version: master 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org As Jonathan and David noted in Bug 25950, Net::Netmask needs a constructor change from 1.9104-2 in order to accept abbreviated formats. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 54

[Bug 26055] New: Advanced Editor Rancor should use "visibility" and not "mandatory" for drawing new records
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '22

05 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26055 Bug ID: 26055 Summary: Advanced Editor Rancor should use "visibility" and not "mandatory" for drawing new records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal 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 The Advanced Editor (Rancor) uses a tag's mandatory flag to decide whether to show in the UI when showing an editor for a new record. This doesn't make 100% sense, since often a cataloguer will also want to see optional fields (like 500) by default to serve as a prompt. In systems like Horizon, one refers to these as "templates". You have a separate set of typical fields for books, journals, DVDs, etc. You don't have to fill in all those fields, but they're the typical fields that you would use for them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11