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

[Bug 18694] New: Translatability: Get rid of exposing [%% FOREACH in csv/ cash_register_stats.tt
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '17

20 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18694 Bug ID: 18694 Summary: Translatability: Get rid of exposing [%% FOREACH in csv/cash_register_stats.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr The file csv/cash_register_stats.tt exposes two FOREACH loops to translation. Translators should not be confronted with code internals. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 18734] New: Internal server error in cash_register_stats.pl when exporting to file
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '17

20 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18734 Bug ID: 18734 Summary: Internal server error in cash_register_stats.pl when exporting to file Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org To reproduce: - Go to Home > Reports > Cash register statistics - Select a date range - Output to screen in browser: Displays OK - Output to a file: Internal Server Error Plack error log says: CGI::param called in list context from package CGI::Compile::ROOT::home_marc_koha_reports_cash_register_stats_2epl line 64, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436. CGI::param called in list context from package CGI::Compile::ROOT::home_marc_koha_reports_cash_register_stats_2epl line 66, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436. exited nonzero: 1 at /home/marc/koha/reports/cash_register_stats.pl line 201. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 17966] New: TT syntax for notices - Prove that ISSUESLIP is compatible
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '17

19 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17966 Bug ID: 17966 Summary: TT syntax for notices - Prove that ISSUESLIP is compatible 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 -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 17014] New: Remove more event attributes from patron templates
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '17

16 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17014 Bug ID: 17014 Summary: Remove more event attributes from patron templates 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 There are many patron-related templates which still use event attributes to define events. These should be modified so that events are defined in JavaScript. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 18409] New: Error when updating pickup library on patron pages
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '17

16 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18409 Bug ID: 18409 Summary: Error when updating pickup library on patron pages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical 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 On the "Check out" and "Details" pages, attempting to update a pickup library from the holds tab results in this alert: "There was an error:error Internal Server Error". This appears to be an issue with the holds rest api not functioning correctly. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[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