November 2016 - Koha-bugs - lists.koha-community.org

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

15 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 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

[Bug 16510] New: When record items exceed OpacMaxItemsToDisplay opacSerialDefaultTab is ignored
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '17

11 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16510 Bug ID: 16510 Summary: When record items exceed OpacMaxItemsToDisplay opacSerialDefaultTab is ignored Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In opac-detail.pl the if construct checks (@itemloop) to see if holdings should be displayed, however, if items exceed OpacMaxItemsToDisplay @itemloop isn't populated and the syspref is ignored my $opac_serial_default = C4::Context->preference('opacSerialDefaultTab'); my $defaulttab = $opac_serial_default eq 'subscriptions' && $subscriptionsnumber ? 'subscriptions' : $opac_serial_default eq 'serialcollection' && @serialcollections > 0 ? 'serialcollection' : $opac_serial_default eq 'holdings' && scalar (@itemloop) > 0 ? 'holdings' : $subscriptionsnumber ? 'subscriptions' : @serialcollections > 0 ? 'serialcollection' : 'subscriptions'; $template->param('defaulttab' => $defaulttab); -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 16130] New: Show the item non-public note on the detail view
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '17

11 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16130 Bug ID: 16130 Summary: Show the item non-public note on the detail view Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We aren't showing the nonpublic note in the intranet detail view. It's useful to have there, so we should show it! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 15745] New: C4::Matcher gets CCL parsing error if term contains ? (question mark)
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '17

08 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15745 Bug ID: 15745 Summary: C4::Matcher gets CCL parsing error if term contains ? (question mark) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org I was using C4::Matcher via the record matching rules during an import, and I kept getting the following error: "CCL parsing error (10014) Embedded truncation not supported ZOOM". Query: id-other,st-urx=http://www.skovdenyheter.se?p=38004 I wondered why it was trying to do "embedded truncation" when it shouldn't have been doing any truncation by default... so I thought about wrapping the whole term in double quotation marks. Sure enough, the following worked and didn't produce an error: id-other,st-urx="http://www.skovdenyheter.se?p=38004" You can notice this same problem elsewhere when using CCL. Most noticeably directly with yaz-client: Z> find ti=test? CCL ERROR: Right truncation not supported Z> find ti="test?" Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 4, setno 2 SearchResult-1: term=test cnt=4 records returned: 0 Elapsed: 0.000816 Also consider the following: Z> find kw,rt=tes* CCL ERROR: Right truncation not supported Z> find kw="tes*" Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 0, setno 23 SearchResult-1: term=tes cnt=0 records returned: 0 Elapsed: 0.000679 Z> find kw,rt="tes*" Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 6, setno 24 SearchResult-1: term=tes cnt=6 records returned: 0 Elapsed: 0.001049 -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 17344] New: Can't set guarantor in quick add brief form
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '17

04 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17344 Bug ID: 17344 Summary: Can't set guarantor in quick add brief form Change sponsored?: --- Product: Koha Version: unspecified 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 When using the quick add feature it's not possible to add a guarantor. To test: - Use quick add form to add a "Kid" (sample patron category) - "Set patron" and search for a patron to link with - Click "choose" - Verify that the guarantor fields in the form remain empty - Open 'full form' - notice some information is there -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 15908] New: Remove use of recordpayment_selectaccts
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '17

30 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15908 Bug ID: 15908 Summary: Remove use of recordpayment_selectaccts 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 -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 16977] New: REST tests cleanup ineffective
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '17

30 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16977 Bug ID: 16977 Summary: REST tests cleanup ineffective Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: larit(a)student.uef.fi QA Contact: gmcharlt(a)gmail.com I'm having issues with REST tests. It seems that whenever the test uses authentication, e.g. my $tx = $t->ua->build_tx(GET => '/api/v1/patrons'); $tx->req->cookies({name => 'CGISESSID', value => $session->id}); $t->request_ok($tx) ... the test does not cleanup database correctly. This can be currently seen in t/db_dependent/api/v1/patrons.t. For holds.t (the other REST test in master at the time of reporting this bug) there is at the moment no authentication and it seems to cleanup nicely. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 15741] New: Incorrect rounding in total fines calculations
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '17

06 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15741 Bug ID: 15741 Summary: Incorrect rounding in total fines calculations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: abl(a)biblos.pk.edu.pl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Our librarians discovered recently that recording payments for some specific fine amounts (64.60, for example) are not working properly - they are getting errors like: You must pay a value less than or equal to 64.60 It's not just 64.60, same thing happens for: 1.14 1.36 1.39 1.57 1.59 1.61 1.64 1.66 1.68 1.82 1.84 1.86 1.89 1.91 1.93 2.01 2.03 2.28 2.47 2.53 2.72 2.78 2.97 ... 32.30 64.10 64.60 65.10 128.20 128.70 129.20 129.70 130.20 130.70 ... and so on. This error seems to be caused by incorrect rounding in C4::Members::GetMemberAccountRecords(). To replicate: 1) Create manual invoice for 64.60 (or 1.14, 1.36, ...) 2) Try to pay it using "Pay amount" or "Pay selected" buttons As a temporary workaround, one may: - pay such amount in 2+ steps (eg. 64.00 + 0.60) - pay individual fines using 'Pay' button[s] on the left but, at first glance at least, an underlying problem for this error may possibly have some more severe consequences than just minor troubles with making payments - eg., if patron has 12+ fines (or credits) of such kind, total account balance calculation may be wrong as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23