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

[Bug 19214] New: Patron clubs: Template process failed: undef error - Cannot use "->find" in list context
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '17

16 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19214 Bug ID: 19214 Summary: Patron clubs: Template process failed: undef error - Cannot use "->find" in list context Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reproduce: 1) Create a club template and a club. 2) Add a user to the club 3) Log in to the OPAC as that user 4) Go to 'your summary' and click the Clubs tab 5) Notice clubs do not load and a warn shows: Template process failed: undef error - Cannot use "->find" in list context at /home/vagrant/kohaclone/Koha/Club/Enrollment.pm line 62. 6) Go to the staff side and go to the member page of that user 7) Go to 'details' and click the Clubs tab 8) Notice clubs do not load and a warn shows: Template process failed: undef error - Cannot use "->find" in list context at /home/vagrant/kohaclone/Koha/Club/Enrollment.pm line 71. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 19208] New: Pay select option doesn't pay the selected fine
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '17

16 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19208 Bug ID: 19208 Summary: Pay select option doesn't pay the selected fine Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.hedstrom.mace(a)sub.su.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 66616 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=66616&action=ed… Fines total amount The "Pay selected" option on the Fines tab in the borrower account page doesn't work as intended. The problem has been noted on both 16.05.00 and on master, but behaves a bit differently. On 16.05 the amount paid will be drawn from the total amount rather than the selected fine, while on master the fine on top of the list gets the amount deducted, even if another fine is choosen from the list. To recreate: 1) Create two or three fines, using the Create manual invoice function. 2) Choose one of the fines (not the one on the top) and click Pay selected 3) Pay a partial amount 4) Go back to the Pay fines tab an notice that the fine you selected has not changed. Instead, either the top fine or the total (see attachment) has ben affected. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 19205] New: Pay selected fine generates 500 error
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '17

16 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19205 Bug ID: 19205 Summary: Pay selected fine generates 500 error 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: andreas.hedstrom.mace(a)sub.su.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Using the pay selected option from the borrowers account, to pay for one specific fine among other gives a 500 error, despite the payment going through. To reproduce: Add two fines using the Create manual invoice function. Select one fine and "pay selected". Pay a part of the amount. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 18046] New: Problem with redirect on logout with CAS
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '17

16 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18046 Bug ID: 18046 Summary: Problem with redirect on logout with CAS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Since updating to 3.22.14 which includes the fix for bug 17841, there is a problem when logging out of the OPAC with CAS. Settings: casLogout = Logout Before the update, you weren't redirected back to the OPAC after logout. Bug 17841 was supposed to fix this behaviour. After the update, we are sending the redirect URL in the service parameter of the logout URL: https://.../logout?url=https%3A%2F%2F...%2Fcgi-bin%2Fkoha%2Fopac-main.pl%3Flogout.x%3D1 The CAS logout itself works, but the redirect to Koha seems to be stuck in an "infinite loop". The page reloads again and again. It seems to work ok, when you craft an URL like: https://.../logout?url=https%3A%2F%2F...%2Fcgi-bin%2Fkoha%2Fopac-main.pl%3Flogout.x%3D1 without the logout.x%3D1 parameter at the end of the URL. Tested in Firefox ESR 45.7.0. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 16293] New: Patron Card Batches documentation is incomplete
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '17

16 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16293 Bug ID: 16293 Summary: Patron Card Batches documentation is incomplete Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Documentation Assignee: nengard(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 50411 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=50411&action=ed… First image in documentation http://manual.koha-community.org/3.22/en/patroncardcreator.html#patroncardb… is missing documentation on how to get to or use the patron card search, which should read as follows: In the 'New batch' or 'Manage batch' screens, patrons may be added by pasting borrowernumbers into the 'Add by borrowernumber(s)' text box. [[insert attached patron_batch_add.png]] Alternatively, clicking on the '+Add patron(s)' button with the 'Add by borrowernumber(s)' field empty will launch a pop-up window containing a patron search screen, which may be used to look up patrons by cardnumber or name [[insert attached patron_batch_search.png]] Clicking the 'Add' link will insert the associated borrowernumber into 'Add by borrowernumber(s)' text box on the 'New batch' or 'Manage batch' screen. You can do as many searches and add as many patrons as you want through the search screen before clicking 'Close'. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 18966] New: Move of checkouts - Deal with duplicate IDs at DBMS level
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '17

14 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18966 Bug ID: 18966 Summary: Move of checkouts - Deal with duplicate IDs at DBMS level Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: blocker 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 Depends on: 18651, 18931 Koha suffers of big bugs due to its history: When data are deleted, they are moved to another tables. For instance issues and old_issues: when a checkin is done, it is moved to the old_issues table. That leads to a main problem that is described on https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix However we tried first to fix the problem (for issues/old_issues) at code level on bug 18242. The goal was to prevent data lost. Data lost may happens in this case: Check an item out (issue_id = 1) Check an item in (issue_id = 1) Restart MySQL (reset auto increment for issue_id to 1) Check an item out (issue_id = 1) Check an item in => BOOM, the issue_id is a PK in old_issues and the move fails. Before bug 18242 the data were lost, we inserted the value into old_issues, which fails silently (because of RaiseError set to 0 in Koha::Database), then delete the row from issues. That has been fixed using a transaction. This patch introduced a regression we tried to fix on bug 18651 comment 0, the patron was charged even if the checkin was rejected. A good way to fix that would have been to LOCK the tables: 1- Start a transaction 2- LOCK the table to make sure nobody will read id and avoid race conditions 3- Move the content from one table to the other, dealing with ids 4- UNLOCK the table 5- Commit the transaction But there were problems using LOCK and DBIx::Class (See commit 905572910b3a - Do no LOCK/UNLOCK the table). Finally the solution implemented is not acceptable for several reasons: - batch checkins may fail - issue_id will always stay out of sync (between issues and old_issues) See 18651 comment 66. Since the next stable releases are very soon, and we absolutely need to fix this problem, I am suggesting to: 1- Execute the move in a transaction to avoid data lost and reject the checkin if we face IDs dup => It will only reject 1 checkin (max is 1 * MySQL restart), no need to deal with race conditions, 2- Display a warning on the checkin page and link to a solution/explanation 3- Communicate as much as we can on the proper fix: Update auto increment values when the DBMS is restarted - https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix 4- Display a warning on the about page for corrupted data (see bug 18931) 5- Write and make available a maintenance script to fix corrupted data (TODO LATER) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18651 [Bug 18651] Move of checkouts is still not correctly handled https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18931 [Bug 18931] Add a "data corrupted" section on the about page -- You are receiving this mail because: You are watching all bug changes.

1 43

[Bug 17784] New: Ability to see funds with an amount of 0.00 when doing a new order
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '17

12 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17784 Bug ID: 17784 Summary: Ability to see funds with an amount of 0.00 when doing a new order Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexandre.breton(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org In the acquisition module, funds with an amount of 0.00$ don’t appear in the dropdown list when doing an new order (in accounting details). To do that, we must put 0.01$ to be able to see the information. Here is the link : cgi-bin/koha/acqui/neworderempty.pl Can we add an option to put funds active or inactive to manage them correctly (and see them in the dropdown list) ? This is usefull to some librairies which must receipt and treat documents for another service through a bigger organization. This other service is in charge of the payment. The document must be present in the list to help librairians to make the follow-up with it. Thanks, Alexandre from CCSR -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 17747] New: Missing extension name .t: /t/db_dependent/ Koha_Elasticsearch.
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '17

12 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17747 Bug ID: 17747 Summary: Missing extension name .t: /t/db_dependent/Koha_Elasticsearch. Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: faceker(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 16942] New: Confirm hold results in ugly error
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '17

12 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16942 Bug ID: 16942 Summary: Confirm hold results in ugly error Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Confirming a hold to set it to waiting will result in an DBIC error in master. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 16493] New: acq matching on title and author
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '17

12 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16493 Bug ID: 16493 Summary: acq matching on title and author Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When you order from a staged file you're getting duplicate warnings that are inaccurate. For example, when you order a file of 50 DVDs for example and they don't have ISBNs they're matching on the books. And then you have to order them one by one. ---------- [11:42] <cait> it seems to use FindDuplicate [11:43] <cait> http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=C4/Search.pm;hb=4… [11:44] <cait> i might be misreading it, but looks like isbn when there is one - if there is none, title and author ----------- This shouldn't happen, it's a big deal in libraries that do a lot of ordering and is just plain wrong based on cataloging rules. Is there any way to override this without doing them one by one or a way to make it use the matching rules instead? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45