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

[Bug 21188] New: t/db_dependent/Circulation/issue.t is failing
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21188 Bug ID: 21188 Summary: t/db_dependent/Circulation/issue.t is failing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Stems from bug 20660 The issue seems to be that $return_date is a string and not a DateTime object - when we call _debar_user_on_return we are expecting a DateTime object -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 21289] New: Error when sending emails to partner libraries
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21289 Bug ID: 21289 Summary: Error when sending emails to partner libraries Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com During the "Place request with partners" workflow, at the point of sending the request mail, an "Internal server error" is displayed and the following is logged: Can't call method "isa" on unblessed reference at /home/koha/kohaclone/ill/ill-requests.pl line 241. The error here is misleading. It is due to the 'catch' block being called without an instance of a Koha::Exceptions::Ill object being passed. The reason it is being called is that the handle_commit_maybe sub is being called inside it. The handle_commit_maybe sub redirects the client, the exits: 295 # Redirect to a view of the newly created request 296 print $cgi->redirect( 297 '/cgi-bin/koha/ill/ill-requests.pl?method=illview&illrequest_id='. 298 $request->id 299 ); 300 exit; This is correct, but because it is being called inside the try block, the "exit" causes the catch block to be called, despite the client being redirected. A patch for this should move the call to handle_commit_maybe outside of the try block, we will still only reach it if everything inside the try block succeeded. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 20981] New: Organization name missing from patron search results
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20981 Bug ID: 20981 Summary: Organization name missing from patron search results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Blocks: 18403 If I search for patrons limited by an institutional patron category, none of the results show a name. git bisect says this bug was introduced by Bug 18403, Use patron-title.inc when hidepatronname is used. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18403 [Bug 18403] Hide patron information if not part of the logged in user library group -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 20991] New: Error will reset category when editing a patron
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20991 Bug ID: 20991 Summary: Error will reset category when editing a patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com - Edit an existing patron - Change the patron category to a category that triggers the error that the user is not in the right age range for that new category - Save, error is triggered - Scroll down - the patron category has been reset -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 20999] New: Remove invalid 'style="block"' from OPAC templates
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20999 Bug ID: 20999 Summary: Remove invalid 'style="block"' from OPAC templates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: trivial 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 a few instances of the invalid 'style="block"' attribute in the OPAC templates. They should be removed. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 20363] New: Privacy management shows misleading "No reading history to delete"
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20363 Bug ID: 20363 Summary: Privacy management shows misleading "No reading history to delete" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org (OPACPrivacy is on) User views the "Your privacy" -page, it shows "No reading history to delete", even when the user has history. This is highly misleading. Error caused by commit 286be46e8a8 -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 20369] New: Analytics search is broken with QueryAutoTruncate set to 'only if * is added'
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20369 Bug ID: 20369 Summary: Analytics search is broken with QueryAutoTruncate set to 'only if * is added' 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: * Disable QueryAutoTruncate * Create an analytic record, add some host items to it * Browser to the analytics tab for the record * Click the link in the 'used in' column of the table * No search results * Enable QueryAutoTruncate * Reload the page, now you get the analytic record -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 20428] New: MARC import fails on Debian Stretch
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20428 Bug ID: 20428 Summary: MARC import fails on Debian Stretch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It appears that Koha cannot access /tmp on Stretch. We should standardize on each Koha instance having it's own TMPDIR in /var/lib/koha/<instance>/tmp to avoid this as well as avoiding possible file name collisions between instances. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 75

[Bug 20455] New: Can't sort patron search on date expired
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20455 Bug ID: 20455 Summary: Can't sort patron search on date expired Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com The patron search hangs when you try to sort by date expired. The error in the Plack logs is: Odd number of elements in anonymous hash at /home/vagrant/kohaclone/C4/Utils/DataTables/Members.pm line 189. output_pref is called with 'dateonly' (ref SCALAR), not a DateTime objectOdd number of elements in anonymous hash at /home/vagrant/kohaclone/C4/Utils/DataTables/Members.pm line 189. To test: - Make sure sample patron data is loaded - Make an empty search for all patrons or another search that gives you a good amount of results - Try to sort on the date expired column -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 20462] New: Duplicate barcodes in batch item deletion cause software error if deleting biblio records.
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '18

24 Oct '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20462 Bug ID: 20462 Summary: Duplicate barcodes in batch item deletion cause software error if deleting biblio records. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To re-create: 1) Create a text file containing duplicate barcodes Here's a quick way to do that, substitute INSTANCE for the instance name of your test server: sudo koha-mysql INSTANCE <<< "select barcode from items where barcode is not null limit 3" | sed '1d;p' > /tmp/dup_barcodes.txt 2) Go to Home › Tools › Batch item deletion 3) Click 'Choose File', select the file you created in step 1. 4) Click 'Continue' 5) Note that duplicate items appear in the list of items to batch delete 6) Check 'Delete records if no items remain' 7) This will trigger a software error Here is the output from the intranet error log: [Thu Mar 22 08:49:35.030497 2018] [cgi:error] [pid 26116] [client x.x.x.x:y] AH01215: [Thu Mar 22 08:49:35 2018] batchMod.pl: CCL parsing error (10014) Search word expected ZOOM for query: hi= at /usr/share/koha/lib/C4/Search.pm line 275., referer: https://intranet.bywatersolutions.com/cgi-bin/koha/tools/batchMod.pl [Thu Mar 22 08:49:35.039872 2018] [cgi:error] [pid 26116] [client x.x.x.x:y] AH01215: [Thu Mar 22 08:49:35 2018] batchMod.pl: DBIx::Class::Storage::DBI::select_single(): Query returned more than one row. SQL that returns multiple rows is DEPRECATED for ->find and ->single at /usr/share/koha/lib/Koha/Objects.pm line 92, referer: https://intranet.bywatersolutions.com/cgibin/koha/tools/batchMod.pl [Thu Mar 22 08:49:35.040735 2018] [cgi:error] [pid 26116] [client x.x.x.x:y] AH01215: [Thu Mar 22 08:49:35 2018] batchMod.pl: Can't call method "items" on an undefined value at /usr/share/koha/intranet/cgi-bin/tools/batchMod.pl line 187., referer: https://intranet.bywatersolutions.com/cgi-bin/koha/tools/batchMod.pl Note that entering the barcodes via the 'scan items one by one' text box removes duplicates in the list, so this only causes problems when uploading a file. It doesn't matter whether you choose duplicate barcodes or duplicate item numbers, both trigger the some error. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16