April 2018 - Koha-bugs - lists.koha-community.org

[Bug 20089] New: Does Koha::Database->schema always return a connected object?
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '19

14 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20089 Bug ID: 20089 Summary: Does Koha::Database->schema always return a connected object? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org My log says no: DBD::mysql::st execute failed: MySQL server has gone away [for Statement "SELECT `me`.`variable`, `me`.`value`, `me`.`options`, `me`.`explanation`, `me`.`type` FROM `systempreferences` `me` WHERE ( `me`.`variable` = ? )" with ParamValues: 0='opacgroupresults'] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1832. I see them quite often, always for preferences. Note that we do not test the cached $database->{schema} in sub schema. If we do, we will however add some time. ( 0.0043 instead of 0.0003 ) What do you think? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 20270] New: SIP2 Connection Issue
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '19

09 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20270 Bug ID: 20270 Summary: SIP2 Connection Issue Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: aniltiwari86(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Created attachment 72087 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=72087&action=ed… SIP Log Hi, We have Installed Koha 17.05.06.000, and created multiple SIP users to integrate with RFID Kiosk. When we are trying to connect with one kiosk it works perfectly. If we try to connect more Kiosk the SIP2 is not responding to 93 packet. Can you please suggest what could be the issue. Regards, Anil -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 19012] New: Note additional columns that are required during patron import
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '19

06 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19012 Bug ID: 19012 Summary: Note additional columns that are required during patron import Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 We say 'branchcode' and 'categorycode' are required - this is true, but so are surname and cardnumber -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 20607] New: Elasticsearch - ability to add a relevancy weight in mappings.yaml file
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '19

06 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20607 Bug ID: 20607 Summary: Elasticsearch - ability to add a relevancy weight in mappings.yaml file Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: claire.hernandez(a)biblibre.com The code could be able to inject mappings and weight if a mapping in mappings.yaml file contains boost-in-simple-search: Exemple: Personal-name: label: Personal-name mappings: - facet: '' marc_field: 100abcdefghjklmnopqrstvxyz marc_type: marc21 sort: ~ suggestible: '' - facet: '' marc_field: 100abcdefghjklmnopqrstvxyz marc_type: normarc sort: ~ suggestible: '' type: '' boost-in-simple-search: 4 4 is added in field weight in table search_field. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 18712] New: Run database_dependent test suite --No ignored
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '19

05 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18712 Bug ID: 18712 Summary: Run database_dependent test suite --No ignored Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: gmcharlt(a)gmail.com Reporter: bob-ewart(a)bobsown.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 63893 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=63893&action=ed… Full log of 'make test' including STDERR and STDOUT Build Koha from the tarball. Answer no to 'run the database-dependent test suite (no, yes) no. Running 'make test' generates many errors trying to access the database. Most of the tests which do generate DBD::mysql::st errors still show up as 'ok'. See the attached log. t/Matcher.t and t/Prices.t do fail Test Summary Report ------------------- t/Matcher.t (Wstat: 768 Tests: 12 Failed: 3) Failed tests: 3-5 Non-zero exit status: 3 t/Prices.t (Wstat: 65280 Tests: 5 Failed: 1) Failed test: 5 Non-zero exit status: 255 Parse errors: Bad plan. You planned 16 tests but ran 5. Files=100, Tests=11528, 95 wallclock secs ( 0.89 usr 0.16 sys + 81.23 cusr 3.06 csys = 85.34 CPU) Result: FAIL Failed 2/100 test programs. 4/11528 subtests failed. Makefile:9572: recipe for target 'test_dynamic' failed make: *** [test_dynamic] Error 255 -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 18224] New: Cleanup after Buug 14778
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '19

05 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18224 Bug ID: 18224 Summary: Cleanup after Buug 14778 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: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Fixtures introduce biblios but they are not used in the whole test case. Remove unnecessary code. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 20654] New: Omnibus: Update two-column templates to use Bootstrap grid
by bugzilla-daemon＠bugs.koha-community.org 04 Aug '19

04 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20654 Bug ID: 20654 Summary: Omnibus: Update two-column templates to use Bootstrap grid Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 14546 This omnibus bug will cover bugs which update two-column template grid markup from YUI to Bootstrap. Typical markup to be replaced: <div id="doc3" class="yui-t2"> <div id="bd"> <div id="yui-main"> <div class="yui-b">  </div> </div> <div class="yui-b">  </div> </div> </div> Replacement: <div class="main container-fluid"> <div class="row"> <div class="col-sm-10 col-sm-push-2">  </div> <div class="col-sm-2 col-sm-pull-10">  </div> </div> </div> Note that "col-sm-push-2" and "col-sm-pull-10" are the classes that reverse the visible column order in the desktop layout. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14546 [Bug 14546] Make staff client templates responsive -- You are receiving this mail because: You are watching all bug changes.

1 103

[Bug 15679] New: Reset item level hold back to record level hold without deleting and readding the hold
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '19

26 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15679 Bug ID: 15679 Summary: Reset item level hold back to record level hold without deleting and readding the hold Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Right now, if a hold is tied to a specific item (for any number of reasons), and it needs to be set back to a title level hold, you have to delete and readd the hold. This is cumbersome enough, but it's even more cumbersome when a record has multiple holds (especially 20+), and the hold has to be replaced and manually back in its original priority order. It would be nice if Koha could allow you to reset a hold back to record level after it's been placed, for all cases, including when it's in transit for a patron. Situations arise where an item arrives damaged or is lost in transit and a new item is needed to fulfill the hold. There should probably be a permission to control access to this proposed functionality, like the existing modify_holds_priority permission. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 16399] New: Renewal information should be logged
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '19

21 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16399 Bug ID: 16399 Summary: Renewal information should be logged Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: misilot(a)fit.edu QA Contact: testopia(a)bugs.koha-community.org Currently cannot * view where (ILS-DI/ Opac / Staff Client) * Who Student/Staff member * When an item was renewed. The only thing tracked is in the issues / old_issues table that an item was renewed on a specific date (no time given) and the total number of renewals. No information is logged as described above. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 15814] New: Templates for MARC modification: Edit action does not work.
by bugzilla-daemon＠bugs.koha-community.org 19 Jul '19

19 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15814 Bug ID: 15814 Summary: Templates for MARC modification: Edit action does not work. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org There is an edit button in the tool for MARC template modification for every action of a template. Expected: click edit for an action, get a form populated with the related values. Actual result: page is scrolled to "Add new action", fields are empty. -- You are receiving this mail because: You are watching all bug changes.

1 27