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

[Bug 28209] New: LostItem should pass skip_record_index to MarkIssueReturned
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28209 Bug ID: 28209 Summary: LostItem should pass skip_record_index to MarkIssueReturned 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com As LostItem can be called in a loop during batch item modifications we should allow for passing through the 'skip_record_index' parameter to MarkIssueReturned Bug 27281 removed the param as it was no longer used and was breaking tests, but we need new code and tests to cover the additional calls -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 28048] New: Getting Internal Server Error while importing Patrons
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28048 Bug ID: 28048 Summary: Getting Internal Server Error while importing Patrons Change sponsored?: --- Product: Koha Version: unspecified Hardware: HP OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: vermanite(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 118917 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=118917&action=e… Screenshot of error Getting Internal Server Error While importing patrons in .CSV format. This error occurs only when I am trying to import new patrons in CSV format. Server Details: OS: Ubuntu 16.04 LTS KOHA Version: 16.11.14.000 MySQL version: mysql Ver 14.14 Distrib 5.7.33 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 28226] New: test message
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28226 Bug ID: 28226 Summary: test message Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Bugzilla Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: gmcharlt(a)gmail.com creating this bug to test emailing; not a real bug -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 28222] New: Option to prefill basket name for a new order
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28222 Bug ID: 28222 Summary: Option to prefill basket name for a new order Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: caroline.cyr-la-rose(a)inlibro.com In training there is always quite a bit of confusion on why the basket name field when creating a new basket/order in Koha is empty and mandatory. Koha generates internally unique IDs, so why does this need to be set? I'd love to get some more information about how other libraries use this field. We also had some requests for a custom order number in a specific pattern to be used there. I wonder if it would be possible to link the field up to something like one of our value_builders.pl. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 28023] New: Typo in Reply-To header
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28023 Bug ID: 28023 Summary: Typo in Reply-To header Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Koha::Email has a typo for the Reply-To header! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 14237] Allow bibs to be added to course without items
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14237 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|tomascohen(a)gmail.com |kyle(a)bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 24940] New: Serials statistics wizard: order vendor list alphabetically
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24940 Bug ID: 24940 Summary: Serials statistics wizard: order vendor list alphabetically Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Currently the vendor pull down in the serials statistics wizard appears to be ordered by vendor id instead of sorting alphabetically by vendor name. This is quite confusing for a longer list. To test: - Add at least 2 vendors: - First: Zzzz - Second: Aaaa - Add subscriptions for each of the vendors - Check the pull down in the serials statistics wizard - Verify it lists them as Zzzz, Aaaa -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 26312] New: Add some error handling during Elasticsearch indexing
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26312 Bug ID: 26312 Summary: Add some error handling during Elasticsearch indexing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Currently Elasticsearch dies if we get an error rather than a response from the ES Client. Generally we can see something like [6056] Committing 5000 records... [Timeout] ** [http://XXX.XXX.XXX.XXX:9200]-[599] Could not write to socket: 'Connection timed out', called from sub Search::Elasticsearch::Role::Client::Direct::__ANON__ at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Indexer.pm line 123. With vars: {' Rather than killing the whole indexing process, we should catch the error, fail the commit, and keep indexing records. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 55

[Bug 8179] Receiving multiple order lines at once
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8179 Ray Delahunty <r.delahunty(a)arts.ac.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |r.delahunty(a)arts.ac.uk -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12017] Move language description out of database
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '21

26 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12017 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au --- Comment #100 from David Cook <dcook(a)prosentient.com.au> --- Thanks for working on this, Bernardo. I think I ignored the language* tables for years until I needed to work on them this past Friday... I'm not sure I follow all the changes across all the patches though. Overall, I was thinking that we could keep a database table in Koha with language codes and the native name for the language. Examples: en, eng, English; zh, chi, 中文. Then we could have a template that defines a hash map which can be used to provide translated versions. For example: [% BLOCK en %]Anglais[% END %] [% BLOCK fr %]Français[% END %] [% langs.en = INCLUDE en %] [% langs.fr = INCLUDE fr %] We could then iterate through the database list and show translated names where possible based on the hash map lookup using the code. -- You are receiving this mail because: You are watching all bug changes.

1 0