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

[Bug 22249] New: Error when submitting Mana comment
by bugzilla-daemon＠bugs.koha-community.org 03 Sep '19

03 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22249 Bug ID: 22249 Summary: Error when submitting Mana comment Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: koha-bugs(a)lists.koha-community.org, testopia(a)bugs.koha-community.org Depends on: 17047 Target Milestone: --- When I submit a Mana comment on a subscription the process completes successfully but in the console this error is returned: Can't locate object method "find" via package "Koha::Resource_comments" (perhaps you forgot to load "Koha::Resource_comments"?) at /home/vagrant/kohaclone/Koha/SharedContent.pm line 89. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17047 [Bug 17047] Mana Knowledge Base : share data -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 21027] New: Totals in statistics tab change when StatisticsFields is changed
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '19

02 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21027 Bug ID: 21027 Summary: Totals in statistics tab change when StatisticsFields is changed 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com As we understand it the totals in the last line of the statistics table in the patron account should be always the same, independent of the selection made in the StatisticsFields system preference. This is not the case. When "location" is removed, the total is less than with "location". I think this might have something to do with the group and empty values for some entries, but have not been able to find the problem yet. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[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 22142] New: An item's current location changes to blank when it is removed from Course Reserves
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '19

28 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22142 Bug ID: 22142 Summary: An item's current location changes to blank when it is removed from Course Reserves Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When removing items from a course reserve, Koha is removing the current location field unless the current location was modified when it was added to the course. Steps: 1.Add an item to an existing active course reserve. 2. Modify Item Type, Shelving Location, Collection code 3. Confirm these changes were made to the item, 4. Remove this item from an active course reserve. 5. See that the item type, shelving location and collection code was reverted to its original value, however, see that the Current Location is now empty. Steps: 1.Add an item to an existing active course reserve. 2. Modify Item Type, Shelving Location, Collection code, and Holding Library 3. Confirm these changes were made to the item, 4. Remove this item from an active course reserve. 5. See that the item type, shelving location and collection code was reverted to its original place, however, see that the Current Location correctly added back. This is happening on 18.05.06, 18.05.07 and 18.11 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[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 20712] New: ILL belongs to the circulation section
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '19

19 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20712 Bug ID: 20712 Summary: ILL belongs to the circulation section Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I belive the ILL handling UI belongs more to the Circulation section than the main staff page. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 20786] New: process_message_queue.pl - multiple subroutine redefined errors
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '19

18 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20786 Bug ID: 20786 Summary: process_message_queue.pl - multiple subroutine redefined errors Change sponsored?: --- Product: Koha Version: 17.11 Hardware: PC OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: mjnkml(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Probably related to bug 2505, in the cronjob email, this comes up: Subject: Cron <root@koha> cd /tmp && koha-foreach --enabled --email /usr/share/koha/bin/cronjobs/process_message_queue.pl Body: Subroutine _ATTRIBUTES redefined at /usr/share/perl5/Authen/CAS/Client/Response/Failure.pm line 13. Subroutine new redefined at /usr/share/perl5/Authen/CAS/Client/Response/Failure.pm line 15. Subroutine code redefined at /usr/share/perl5/Authen/CAS/Client/Response/Failure.pm line 17. Subroutine message redefined at /usr/share/perl5/Authen/CAS/Client/Response/Failure.pm line 18. Subroutine new redefined at /usr/share/perl5/Authen/CAS/Client/Response/Success.pm line 13. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 22129] New: Report 1.3.3 Patrons Whose Age Violates Category Age Limits (finds nothing /is faulty)
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '19

18 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22129 Bug ID: 22129 Summary: Report 1.3.3 Patrons Whose Age Violates Category Age Limits (finds nothing /is faulty) Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: Heinrich.Hartl(a)email.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The report is faulty: For MaxAge a value specified correctly in the category is overidden and replaced by 999. Therefore no violation of MaxAge is found by this report. I made a quick and dirty correction: $ diff Rep* 7c7,8 < GREATEST ( c.upperagelimit, 999 ) AS MaxAge, --- > # GREATEST ( c.upperagelimit, 999 ) AS MaxAge, > c.upperagelimit AS MaxAge, 19c20,23 < # age NOT BETWEEN MinAge AND MaxAge --- > age < MinAge or ( age > MaxAge And Maxage > 0 ) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

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