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

[Bug 19719] New: Add a ‘Collection’ column in the patron loans data table.
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '19

02 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19719 Bug ID: 19719 Summary: Add a ‘Collection’ column in the patron loans data table. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jesse(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org 1 - Add the Collection code (ccode) to the issues table -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 19506] New: Staged Marc Import should warn if the selected encoding does not match MARC 21 leader
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '19

23 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19506 Bug ID: 19506 Summary: Staged Marc Import should warn if the selected encoding does not match MARC 21 leader Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Mis-matches between character encodings will cause diacritics be incorrectly imported into Koha. If the imported marc record is MARC8 encoded and imported as UTF-8, diacritics will be converted to the REPLACEMENT CHARACTER '�'. A UTF-8 encoded file imported as MARC8 will try to render the multi-byte UTF-8 characters as MARC8, resulting in garbage text. MARC21 stores its encoding in leader position 09 - Character coding scheme (http://www.loc.gov/marc/bibliographic/bdleader.html) The accepted encodings are '#' for MARC8 and 'a' for UTF-8 (although Koha exports ' ' for MARC8). Koha should check the leader for MARC21 records and warn if the selected encoding does not match the encoding of the marc record, giving the user the opportunity to change the encoding or download fresh records with the correct encoding. [I couldn't tell if this was an issue for UNIMARC] -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 16660] New: Elasticsearch broken if OpacSuppression is activated
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '19

17 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16660 Bug ID: 16660 Summary: Elasticsearch broken if OpacSuppression is activated Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When OpacSuppression is active, you can't search using Elasticsearch. The error shown is: Unable to perform your search. Please try again. By adding a die we coaxed it into a better error message: Can't use string ("(HASH(0xcfe2548)) not Suppress=1") as a HASH ref while "strict refs" in use at /home/katrin/kohaclone/Koha/SearchEngine/Elasticsearch/Search.pm line 99. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 16690] New: Installing DB on remote server fails without *.* permissions
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '19

17 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16690 Bug ID: 16690 Summary: Installing DB on remote server fails without *.* permissions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: mtompset(a)hotmail.com Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org KohaDB: 192.168.71.250 > CREATE DATABASE koha_ils; > GRANT ALL ON koha_ils.* TO 'kohauser'@'192.168.71.251' IDENTIFIED BY 'kohapass'; > FLUSH PRIVILEGES; > QUIT; KohaApp: 192.168.71.251 Do an install. Hack the kohaconf username, hostname, passwords to match. Try to run the web install steps. You will get told you don't have enough permissions. Why? Because 'hostname' is 192.168.71.250 to connect to the DB, but the app server is 192.168.71.251, and you should be checking against those GRANTS in installer/install.pl around line 116. Hacked in a <webserver> tag to the kohaconf and used that value instead in the script. Everything works. -- You are receiving this mail because: You are watching all bug changes.

1 41

[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 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 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 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