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

[Bug 21737] New: 18.05 manual needs documentation on Grouping of Libraries
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '19

24 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21737 Bug ID: 21737 Summary: 18.05 manual needs documentation on Grouping of Libraries Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This has changed in the Koha version of 18.05. There is documentation needed on this for the new 18.05 manual. This is the bug: [15707] Add ability to define hierarchical groups of libraries -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 20113] New: Show statistic fields on spend and ordered reports
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '19

23 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20113 Bug ID: 20113 Summary: Show statistic fields on spend and ordered reports 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org On the acquisitions start page the amounts ordered and spent for each fund are linked to a list of the connected orders. It would be nice if this list also displayed the statistics1 and statistics2 values from the order. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 20664] New: Optimize retrieval of biblio and item data
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20664 Bug ID: 20664 Summary: Optimize retrieval of biblio and item data Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: ere.maijala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org There are several inefficiencies in the current process of retrieving biblios and embedding items in the MARC data. These affect especially batch processes such as exporting of records and the OAI-PMH provider. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 118

[Bug 21028] New: www/history.t is failing on jenkins for Ubuntu 18.04
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21028 Bug ID: 21028 Summary: www/history.t is failing on jenkins for Ubuntu 18.04 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com, mirko(a)abunchofthings.net, nick(a)bywatersolutions.com, tomascohen(a)gmail.com t/db_dependent/www/history.t is failing with the following error on Ubuntu 18.04 (at least with the image from koha-testing-docker): koha_1 | # Failed test 'Cyrillic characters with umlauts show correctly on the history page.' koha_1 | # at t/db_dependent/www/history.t line 68. It is *not* an encoding issue, the problem is that history.txt is not found: Could not read the history.txt file. Please make sure <docdir> is correctly defined in koha-conf.xml. >From koha-conf.xml: <docdir>/usr/share/doc/koha-common</docdir> Indeed this location does not contain history.txt: root@95f30c756223:/kohadevbox/koha# ls /usr/share/doc/koha-common changelog.Debian.gz copyright I have no idea if it is a koha issue, a packaging issue, or a koha-testing issue. Does anyone has an idea? https://jenkins.koha-community.org/job/Koha_18.05_U18/14/consoleFull -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 18549] New: There should be a warning that logging out of Koha will leave browser session logged in to OAuth
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18549 Bug ID: 18549 Summary: There should be a warning that logging out of Koha will leave browser session logged in to OAuth Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org >From bug 16892 Nick: For CAS we have casLogout - can we have something similar here? I think disconcerting if a patron signs in via google, signs out of Koha and walks away leaving their google auth intact unintentionally Mark: This is the problem. If you have multiple tabs, let's say gmail in one, and Koha in the other. If Koha does a forced logout, then your gmail tab will be affected. This is the problem that is widely known. I was thinking of actually doing another bug to drop-down choose what kind of log out. Martin: A federated logout is actually pretty rare in my experience, though it is possible. As you say Mark, it 'feels' strange to the user that logging out of seemingly unrelated apps can have the knock on effect of logging out apps in other tabs that happen to share an aouth2 openid connect identity provider. On a related note, I'm not sure I saw any code out end to support such a federated logout triggered by another service in our end either... but perhaps I missed it ;) Nick: Perhaps if OAuth is activated just a note added that when you log out of Koha you may still be logged in via google? I agree a user with many tabs open may not expect this, but a patron using a shared machine in the library who signs in to place a hold or renew may never visit their email or expect that they have signed in to that. I think a pop-up when logging out to say "Hey, you are logged in to google, and they know lots of stuff about you" wouldn't hurt, who can say if it would help :-) Mark: Perhaps this type of discussion should happen on another bug report, as this bug has nothing to do with logging out. :) Also, yes, some sort of warning should be displayed, somewhere, somehow. Nick: It can happen here now :-) -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 22905] New: Edit suggestions - wrong branchcode behavior
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '19

21 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22905 Bug ID: 22905 Summary: Edit suggestions - wrong branchcode behavior Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions 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: 22368 Target Milestone: --- Because of the "Library" filter on the left of the "Suggestions management" screen, there is something wrong happening: 1. Create a suggestion from library A, login from library B 2. Go to Home › Acquisitions › Suggestions management => The suggestion does not appear - OK 3. In the filter on the left, select "all library" => The suggestion appears on the pending tab - KO 4. Select the suggestion and mark is as 'Accepted' => => The suggestion still appears on the pending tab - Failure The log says: DBD::mysql::st execute failed: Cannot add or update a child row: a foreign key constraint fails (`koha_kohadev`.`suggestions`, CONSTRAINT `suggestions_ibfk_branchcode` FOREIGN KEY (`branchcode`) REFERENCES `branches` (`branchcode`) ON DELETE SET NULL ON UPDATE CASCADE) [for Statement "UPDATE `suggestions` SET `accepteddate` = ?, `branchcode` = ?, `currency` = ?, `manageddate` = ?, `price` = ?, `reason` = ?, `suggesteddate` = ?, `total` = ? WHERE ( `suggestionid` = ? )" with ParamValues: 0='2019-05-14T15:48:18', 1="", 2="CAD", 3='2019-05-14T15:48:18', 4="0.00", 5="", 6='2019-05-14T00:00:00', 7="0.00", 8=3] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1836. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22368 [Bug 22368] Table suggestions lacks foreign key constraints -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 22585] New: CAS login link for staff intranet is double-escaped
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '19

21 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22585 Bug ID: 22585 Summary: CAS login link for staff intranet is double-escaped Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: jrittenh(a)nd.edu QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Target Milestone: --- Created attachment 87036 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=87036&action=ed… remove double-escape for CAS URL The return URL that is part of the link to CAS login is double-escaped on the staff login page. This means that %3A%2F%2F is converted to %253A%252F%252F. It appears that this is the same issue as bug 21973 but in the staff intranet template. I have attached an identical patch for the intranet auth.tt file. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 22546] New: MaxFine is not recorded in HEA
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '19

21 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22546 Bug ID: 22546 Summary: MaxFine is not recorded in HEA Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Websites, Mailing Lists, etc Assignee: wizzyrea(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- I'm not sure how the whitelist of prefs being sent to HEA was constructed and whether there's anything in place to maintain it :( But, I'd be really interested to see what the usage of the MaxFine preference is in the wild. The code that implements it is somewhat confusing but it's nature and appears to take into account non-fine amounts which I would not have expected. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 22602] New: OverDrive circulation integration is broken when user is referred to Koha from another site
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '19

17 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22602 Bug ID: 22602 Summary: OverDrive circulation integration is broken when user is referred to Koha from another site Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- To recreate: 1 - Have a working OverDrive account and setup 2 - Put a link to your koha site on another site and follow the link to open Koha in a new tab.window 3 - Do an overdrive search 4 - Note that copies listed as available are correct, however, all items only have a place hold button The issue is in the code below - if we came from an outside site we cannot access p and we 'return' which never instantiates checkout_popup which is needed for creating the checkout buttons later 87 var checkout_popup = null; 88 $( document ).ready(function() { 89 var p = window.opener; 90 if (p) { 91 try { cb = p.refresh_overdrive_account_details;} 92 catch(err){ return; } //Catch error if opener is not accessible 93 if (cb) { 94 cb(); 95 } else { 96 p.location.reload(); 97 } 98 window.close(); 99 } 100 checkout_popup = $("#overdrive-checkout"); 101 $("#overdrive-login-form").submit(function(e){ 102 e.preventDefault(); 103 $("#overdrive-login").modal('hide'); 104 var ODpassword = $("input[name='ODpassword']").val(); 105 login( ODpassword ); 106 }); 107 }); -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 18710] New: Wrong subfield modified in batch item modification
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '19

17 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18710 Bug ID: 18710 Summary: Wrong subfield modified in batch item modification Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In Tools > Batch item modification, one can modify or delete a subfield. When deleting a subfield et modifying another, the wrong subfield gets modified. -- You are receiving this mail because: You are watching all bug changes.

1 35