May 2017 - Koha-bugs - lists.koha-community.org

[Bug 17234] New: ALTER IGNORE TABLE is invalid in mysql 5.7. This breaks updatedatabase.pl
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '19

18 Jan '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17234 Bug ID: 17234 Summary: ALTER IGNORE TABLE is invalid in mysql 5.7. This breaks updatedatabase.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: gmcharlt(a)gmail.com Reporter: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Since mysql 5.7, IGNORE is invalid in ALTER statements. This breaks updatedatabase.pl with errors like BD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IGNORE TABLE suggestions ADD KEY status (STATUS)' at line 1 [for Statement " ALTER IGNORE TABLE suggestions ADD KEY status (STATUS) "] at ./installer/data/mysql/updatedatabase.pl line 10420. DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IGNORE TABLE suggestions ADD KEY biblionumber (biblionumber)' at line 1 [for Statement " The patch will simply remove the IGNORE statement 11 times in updatedatabase.pl -- You are receiving this mail because: You are watching all bug changes.

1 86

[Bug 17765] New: Hide 'Holds' link in staff result list when user has no permission to place holds
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '19

17 Jan '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17765 Bug ID: 17765 Summary: Hide 'Holds' link in staff result list when user has no permission to place holds Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff Client 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 The "Holds" link on the staff result list is still visible, even if the user has no "reserveforothers" permission. At the same time it's not possible to place a hold from the detail page and you get a permission error when trying to use the link. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 18408] New: Remainder of title (245$b) in Koha::Biblio
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '19

16 Jan '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18408 Bug ID: 18408 Summary: Remainder of title (245$b) in Koha::Biblio Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 18102] New: REST API: Add pickup_location to library' s Swagger definition
by bugzilla-daemon＠bugs.koha-community.org 15 Jan '19

15 Jan '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18102 Bug ID: 18102 Summary: REST API: Add pickup_location to library's Swagger definition Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Bug 7534 adds a column "pickup_location" to branches table. This column can be configured at cgi-bin/koha/admin/branches.pl. If disabled, it removes the library from list of available pickup locations when placing a hold. This Bug will add the proposed column to api/v1/swagger/definitions/library.json. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 18396] New: UK format dates not sorting correctly
by bugzilla-daemon＠bugs.koha-community.org 14 Jan '19

14 Jan '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18396 Bug ID: 18396 Summary: UK format dates not sorting correctly Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 61956 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=61956&action=ed… Screenshot showing UK date sorting problem When you view a user with a large number of checkouts, and you sort the checkouts by date issued, if the system uses UK date format (DD/MM/YYYY) the sorting doesn't working correctly - for example, you might see: 02/02/2017 03/03/2017 08/02/2017 10/01/2017 16/12/2016 instead of the correct order, which would be: 16/12/2016 10/01/2017 02/02/2017 08/02/2017 03/03/2017 See attached screenshot for a real example. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 16558] New: Option to choose to include or exclude bibs without items when exporting records
by bugzilla-daemon＠bugs.koha-community.org 14 Jan '19

14 Jan '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16558 Bug ID: 16558 Summary: Option to choose to include or exclude bibs without items when exporting records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: sfayle(a)roseman.edu QA Contact: testopia(a)bugs.koha-community.org The addition of an option to "don't export" or "export" bibs without items in the export data tool. Some libraries may need to export only bibs without items or conversely they may want to only export bibs with items. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 16666] New: TagsExternalDictionary is a rather confusing preference name
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '19

11 Jan '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16666 Bug ID: 16666 Summary: TagsExternalDictionary is a rather confusing preference name Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com You do not pass an external dictionary (file) into this syspref. You actually pass the location of ispell on your box. If you have ispell but do not enter its path here, the pref does not trigger the spell check. So it is also enable/disable ispell. Tags.pm requires the Ispell module; it is not a mandatory depends. Furthermore the pref description says: Allow tags in the dictionary of the ispell executable on the server to be approved without moderation. So I would not mind a better name :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 15899] New: Remove the use of recordpayment
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '19

10 Jan '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15899 Bug ID: 15899 Summary: Remove the use of recordpayment Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org With recordpayment now simply being a wrapper round Koha::Account::pay, we can remove the calls to recordpayment and replace them with direct calls to Koha::Account::pay. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 18580] New: Account-pay does not apply credits / clear old fines as did recordpayment
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '19

10 Jan '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18580 Bug ID: 18580 Summary: Account-pay does not apply credits / clear old fines as did recordpayment 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: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com the recordpayment routine in C4::Accounts cleared old paid fines and applied credit amounts as part of its pay routine. The behaviour was implicit and not signalled or commented in the code. The pay routine in Koha::Account which is now called by paycollect.pl instead of the old routine does not leaving these on the users fine display although they owe 0. Staff cannot manually remove these. For example a user has the following accountlines +-----------+-------------+-------------------+ | amount | accounttype | amountoutstanding | +-----------+-------------+-------------------+ | -1.300000 | C | -1.300000 | | 0.650000 | Res | 0.650000 | | 0.650000 | Res | 0.650000 | | 0.650000 | Res | 0.650000 | +-----------+-------------+-------------------+ after recordpayment has been called with an amount of 0.65 the lines are +-----------+-------------+-------------------+ | amount | accounttype | amountoutstanding | +-----------+-------------+-------------------+ | -1.300000 | C | 0.000000 | | 0.650000 | Res | 0.000000 | | 0.650000 | Res | 0.000000 | | 0.650000 | Res | 0.000000 | | -0.650000 | Pay | 0.000000 | +-----------+-------------+-------------------+ However now calling Account->pay for the same amount results in +-----------+-------------+-------------------+ | amount | accounttype | amountoutstanding | +-----------+-------------+-------------------+ | -1.300000 | C | -1.300000 | | 0.650000 | Res | 0.000000 | | 0.650000 | Res | 0.650000 | | 0.650000 | Res | 0.650000 | | -0.650000 | Pay | 0.000000 | +-----------+-------------+-------------------+ leaving the credit and two fines with an amountoutstanding although the user has nothing to pay (the amountoutstanding columns sum to 0) and leading to misleading displays. The difference is driven by the line where @outstanding_fines is retrieved the selection is amountoutstanding > 0. In recordpayment it was amountoutstanding <> 0 so that negative amounts were included and processed as part of the payment, rather than ignored. The fact that this implicit behaviour was not commented made it easy to miss. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 18531] New: REST api: Add an endpoint for use by GOBI
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '19

09 Jan '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18531 Bug ID: 18531 Summary: REST api: Add an endpoint for use by GOBI Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org GOBI (formely YBP) is an aquisitions management system. It handles most of the acquisitions workflow, and traditionally generated MARC files to be included on the institution's library systems. Those files were usually served on an FTP server, for the institution to download and import on their ILS. GOBI implemented what they call GOBIapi, which is a simple workflow for them to directly inject that acquisitions information and resulting records through the use of webservices. In Koha, this means having an endpoint accepting GOBI order messages (in their documented XML format) and have it follow the internal Koha workflow for baskets: - Create a basket - Fill it with the record and budget information, etc - Close the basket and mark it as received. - Deal with the received MARC data. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9