September 2020 - Koha-bugs - lists.koha-community.org

[Bug 26260] New: elasticsearch>cnx_pool missing in koha-conf-site.xml.in
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '20

29 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26260 Bug ID: 26260 Summary: elasticsearch>cnx_pool missing in koha-conf-site.xml.in Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 22705 Added by bug 22705, but only in etc/koha-conf.xml Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22705 [Bug 22705] Change default value of Elasticsearch cxn_pool to 'Static' -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 24780] New: 952$i stocknumber does not display in batch item modification
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '20

29 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24780 Bug ID: 24780 Summary: 952$i stocknumber does not display in batch item modification Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When trying to edit items via batch item modification, the subfield i does not display. To recreate, add a value to 952$i, then add that barcode to the batch item modification function. You will see the value display in the item summary across the top of the screen, but the $i does not show in the edit section below. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 26224] New: Prevent double submit of header checkin form
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '20

29 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26224 Bug ID: 26224 Summary: Prevent double submit of header checkin form 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 Same as bug 26136, but for the checkin form in the header -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 26414] New: Unable to export Withdrawn status using CSV profile
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '20

29 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26414 Bug ID: 26414 Summary: Unable to export Withdrawn status using CSV profile 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When using CSV profiles to export MARC records, it is impossible to export the withdrawn status. I suspect it is because withdrawn is in 952$0 and 0 is considered null rather than an actual 0. To replicate: 1) Go to Tools > CSV profiles 2) Click on New CSV profile 3) Enter a profile name (ex. Simple record) 4) In the Profile MARC fields field enter the following (for MARC21) 245a|100a|952o|9520 5) Save your profile 6) Go to Search and search for something 7) Add a couple of things in your cart 8) Go to your cart 9) Click on Download and choose your CSV profile 10) Open the file and notice the 9520 column contains the whole of the 952 field and not just the withdrawn status I tried with different ways to write the MARC fields, but 952$0 just never shows alone. 245a|100a|952o|Withdrawn=952$0 245a|100a|952o|952$0 Caroline -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 25810] New: Stage MARC records for import progress meter sticks at 0%
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '20

29 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25810 Bug ID: 25810 Summary: Stage MARC records for import progress meter sticks at 0% Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: Boze.1(a)nd.edu QA Contact: testopia(a)bugs.koha-community.org Created attachment 106031 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=106031&action=e… Gateway time-out error during staging records This is somewhat similar to bug 1816 and bug 18719. We are using Koha 18.11 and upgrading to 19.11, and experience it in both versions. We are importing large sets of biblios on a quarterly basis, around 70,000 records broken into files of 10,000. In the "Stage MARC for import" tool, after clicking the "Stage for import" button, the progress meter sticks at 0%. After about 90 seconds a popover message displays with a "504 Gateway Timeout" and an error saying that the import of records failed. The page doesn't update further, although after waiting a sufficiently long period of time, the "Staged MARC management" tool shows that the records have been staged. We are using nginx as a load balancer, which is what I suspect causes the gateway timeout error. If the progress meter were receiving data to update it, this would probably prevent the timeout and the page would finish uninterrupted. I'm attaching an image of the error. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 25665] New: test t/db_dependent/Circulation.t fails on a specific date
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '20

28 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25665 Bug ID: 25665 Summary: test t/db_dependent/Circulation.t fails on a specific date Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org 2020-06-02 == Test plan == Warning: changing the system time to something too far in the past will disrupt HTTPS & TLS so you will have errors if you try to browse the web in parallel. And other software(like email clients) might pop errors. Nothing to worry about. 1. Set system date to 2020-06-01 (time: somewhere during that day) 2. prove t/db_dependent/Circulation.t 3. "All tests successful." 4. Set system date to 2020-06-02 (time: somewhere during that day) 5. prove t/db_dependent/Circulation.t 6. Fail 7. Set system date to 2020-06-03 (time: somewhere during that day) 8. "All tests successful." master : doesn't happen 19.11.x: doesn't happen 19.05.x: happens (v19.05.11) -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 25037] New: Add support for multiple checkout types
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '20

28 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25037 Bug ID: 25037 Summary: Add support for multiple checkout types Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This is a blocker to Bug 24101. As of now we have two checkout types, a normal checkout and an on-site checkout type. In order to target circulation rules to a specific checkout type, the issues table must have information on which type of checkout it is. On-site checkout is currently determined by a boolean value in issues.onsite_checkout database column. For supporting multiple checkout types, we should convert this column into a generic checkout_type field. This Bug also sets an easy-to-extend base for further checkout types. In theory a library could define any types of checkouts dynamically, but support for that is outside the scope of this Bug. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 79

[Bug 25089] New: Add checkout_type to circulation rules
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '20

28 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25089 Bug ID: 25089 Summary: Add checkout_type to circulation rules Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This is a follow-up to Bug 25037. In that Bug we enabled issues to contain data on its checkout type. In this Bug we will add support for defining circulation rules for those types. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 88

[Bug 25957] New: Elasticsearch 5.X - empty subfields cause error on suggestible fields
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '20

27 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25957 Bug ID: 25957 Summary: Elasticsearch 5.X - empty subfields cause error on suggestible fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com To recreate: 1 - Load the sample DB or edit a record (using advanced cataloging editor) to have a blank subfield in a field that is indexed as suggestible 2 - For example 'author' / 100a 100 _ _ ‡a 3 - Index that record into Elasticsearch 5.X: perl misc/search_tools/rebuild_elasticsearch.pl -v -bn 115 -b -d 4 - Note error 'value must have length > 0' 5 - Edit mappings to set author 100a not suggestible 6 - perl misc/search_tools/rebuild_elasticsearch.pl -v -bn 115 -b -d 7 - Success -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 26245] New: Remove unused functions from members.js
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '20

27 Oct '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26245 Bug ID: 26245 Summary: Remove unused functions from members.js 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 Blocks: 26244 There are several functions in members.js which are obsolete and unused. Rather than change them in the process of fixing Bug 26244 they should be removed. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26244 [Bug 26244] Move translatable strings out of memberentrygen.tt and into JavaScript -- You are receiving this mail because: You are watching all bug changes.

1 11