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

[Bug 21457] New: datelastseen and datelastborrowed out of sync
by bugzilla-daemon＠bugs.koha-community.org 26 May '19

26 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21457 Bug ID: 21457 Summary: datelastseen and datelastborrowed out of sync 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In the items table we have these two columns: - datelastborrowed - the date the item was last checked out/issued - datelastseen - the date the item was last see (usually the last time the barcode was scanned or inventory was done) Based on these descriptions you would expect that datelastseen was always the same as or more recent than datelastborrowed, right? One of our customer libraries just made me aware that this is not always the case. This SQL finds the unexpected data: SELECT COUNT(*) FROM items WHERE datelastborrowed > datelastseen; Three of our sites have this unexpected data. They all use SIP2. But we also have a couple sites that use SIP2 that do *not* have unexpected data, so that might be a false lead. Anyone else seen this? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 22010] New: RecordedBooks and OverDrive should check preferences over passing variables
by bugzilla-daemon＠bugs.koha-community.org 24 May '19

24 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22010 Bug ID: 22010 Summary: RecordedBooks and OverDrive should check preferences over passing variables Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Currently RecordedBooks circulation throws an error on the user account page for 'SPINNER_THROBBER' undefined The param is not passed to the template on that page - rather than passing it we should make the checks in the template -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 22357] New: Every run of runreport.pl with --store-results creates a new row in saved reports
by bugzilla-daemon＠bugs.koha-community.org 24 May '19

24 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22357 Bug ID: 22357 Summary: Every run of runreport.pl with --store-results creates a new row in saved reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 Target Milestone: --- While testing bug 22323 I noticed an issue with the reports table in combination with stored results. Stealing a part of the test plan: 1) Create a new item with itemnotes 'accentué' 2) Create a report and note the report number ... 5) Run from command line (replace X by report number) : misc/cronjobs/runreport.pl X --format=csv --csv-header --store-results ... 7) Go to saved reports table 8) Look at the table, each run of the cronjob will create a new row in the table instead of just updating the saved results column. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 21589] New: Series link formed from 830 field is incorrect
by bugzilla-daemon＠bugs.koha-community.org 24 May '19

24 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21589 Bug ID: 21589 Summary: Series link formed from 830 field is incorrect Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 13692 corrected the series link for records using a 490/800 combination When a record has a 490/830 conbination for series, the link is malformed (title is used as author, title is blank) -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 20692] New: koha-plack doesn't check for Include *-plack.conf line in /etc/apache2/sites-available/$ISNTANCE.conf
by bugzilla-daemon＠bugs.koha-community.org 24 May '19

24 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20692 Bug ID: 20692 Summary: koha-plack doesn't check for Include *-plack.conf line in /etc/apache2/sites-available/$ISNTANCE.conf Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: ropuch(a)bagno.be QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz When enabling Plack, koha-plack uncomment plack related Include in instance's apache conf. Little problem occurs when old pre-plack configs are used, without required Include lines. In this case koha-plack still report success, with no change done. So in the end we have running Plack, but it's doing nothing. plack.log is empty, but there is an entry in plack-error.log that can trick people into thinking they have Plack properly configured and running: 2018/05/01-21:06:27 Starman::Server (type Net::Server::PreFork) starting! pid(10257) Binding to UNIX socket file "/var/run/koha/galway/plack.sock" Setting gid to "1001 1001" Setting uid to "1001" koha-plack:enable_plack() should check if Plack lines exists before trying to uncomment them and either fail with warn message, or add them. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 22339] New: Elasticsearch - fixed field mappings should match MARC ranges
by bugzilla-daemon＠bugs.koha-community.org 24 May '19

24 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22339 Bug ID: 22339 Summary: Elasticsearch - fixed field mappings should match MARC ranges 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 Target Milestone: --- ff7-00 is set to: 007_/1 it should be mapped to position 0 I believe any other specific character positions should be checked to ensure they are corect as well To recreate: 1 - Find an item with an 007 in your catalog 2 - Make sure it is indexed in ES 3 - View the ES record: kohadevbox curl 'localhost:9200/koha_kohadev_biblios/data/19?pretty=yes' | grep -A7 ff7 koha testing docker curl 'es:9200/koha_kohadev_biblios/data/19?pretty=yes' | grep -A7 ff7 adjust for other setups 4 - Note the 00 indexes the 01 position, etc -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 19241] New: Items with status of hold show as available in cart
by bugzilla-daemon＠bugs.koha-community.org 24 May '19

24 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19241 Bug ID: 19241 Summary: Items with status of hold show as available in cart Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: michael(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 66784 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=66784&action=ed… attachment shows item with status on hold in cart showing as available Items that have status of on hold show as available on cart list. While users can observe the item has the status of on hold before putting it in the cart, it was reported some patrons find this inconsistency confusing. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 19302] New: Pass objects to IsAvailableForItemLevelRequest
by bugzilla-daemon＠bugs.koha-community.org 24 May '19

24 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19302 Bug ID: 19302 Summary: Pass objects to IsAvailableForItemLevelRequest Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Pass Koha::Item and Koha::Patron to C4::Reserves::IsAvailableForItemLevelRequest -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 20929] New: koha-dump should not pass a --password argument to mysqldump
by bugzilla-daemon＠bugs.koha-community.org 23 May '19

23 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20929 Bug ID: 20929 Summary: koha-dump should not pass a --password argument to mysqldump Change sponsored?: --- Product: Koha Version: master Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: solaris.smoke(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Created attachment 76017 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=76017&action=ed… Use env variable instead of --password argument for mysqldump koha-dump currently passes a password as a CLI argument to mysqldump, which results in the following warning: mysqldump: [Warning] Using a password on the command line interface can be insecure. Depending on how a server is configured, this results in emails being sent to the administrator every time the cron job runs. It's trivial to change this to pass an environment variable instead, so as not to trigger the warning. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 21964] New: Switch two-column templates to Bootstrap grid: Patrons part 2
by bugzilla-daemon＠bugs.koha-community.org 23 May '19

23 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21964 Bug ID: 21964 Summary: Switch two-column templates to Bootstrap grid: Patrons part 2 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: 20654 These two-column patron templates can be updated to use the Bootstrap grid. - modules/members/maninvoice.tt - modules/members/member-flags.tt - modules/members/member-password.tt - modules/members/member.tt - modules/members/memberentrygen.tt Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20654 [Bug 20654] Omnibus: Update two-column templates to use Bootstrap grid -- You are receiving this mail because: You are watching all bug changes.

1 16