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

[Bug 17812] New: Check out error made by the cursor not returning at " enter item barcode" space
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '17

11 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17812 Bug ID: 17812 Summary: Check out error made by the cursor not returning at "enter item barcode" space 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: alexandre.breton(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some people have not save loans because they forgot to clic again on "enter item barcode" space after taking the option "on-site check out" 1)Go to Circulation module 2)Go to checkouts 3)Select a valid user for a loan 4)Observe the cursor is in "enter item barcode" space 4)Select the option "on-site check out" 5)Observe that the cursor isn't returning to "enter item barcode space" by itself Eliminate this additionnal clic can save lot of time to people doing many loans at a same time. Thanks for the support, Alexandre from CCSR -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 18331] New: Export csv in item search, exports all items in one line (see Bug 16914)
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '17

10 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18331 Bug ID: 18331 Summary: Export csv in item search, exports all items in one line (see Bug 16914) Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr CSV exports of late orders and item search are broken again if you are using them from a 'complete' translation. The theory is that if the strings are not translated, then the file is only copied (preserves line breaks) and not translated (kills line breaks). Both late orders and item search csv expots are effected. For item search there is one string in itemsearch_item.csv.inc: %s %s %s %s "%s %svon %s%s", "%s", "%s", "%s", "%s", "%s", "%s", "%s", "%s", "%s", "%s", "%s" Easiest way to test: - Install German - Test CSV export - it should be broken. - Look for the strings in itemsearch_item.csv in the staff po file and "untranslate" them. This is easiest done by adding "fuzzy". - Reinstall German - CSV shoudl be fixed -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 62

[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 18466] New: No article requests breaks the opac-user-views block
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '17

08 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18466 Bug ID: 18466 Summary: No article requests breaks the opac-user-views block 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: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org Created attachment 62508 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=62508&action=ed… screenshot If you have no open article requests, the tabbed box with checked out items, article requests. etc. just below the patron's name is awkward looking when you click on the article requests tab: the box below the tabs disappears because the way the `[% IF Koha.Preference('ArticleRequests') && IF borrower.article_requests_current.count %]` condition is written no table is printed at all. Sorry if I'm articulating this poorly, a screenshot is attached. Patch coming shortly, I'm just going to mimic the behavior of the checked out items section when there are no checked out items. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 18179] New: Patron Restrictions not showing on member detail page
by bugzilla-daemon＠bugs.koha-community.org 07 Sep '17

07 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18179 Bug ID: 18179 Summary: Patron Restrictions not showing on member detail page Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com When a borrower has a restriction applied, the Restrictions tab on the Details screen doesn't show the restriction is there even though there's a message at the top of the screen saying the account is restricted. This does appear correctly on the circulation page. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 66

[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 17864] New: Increase coverage on admin pages
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '17

01 Sep '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17864 Bug ID: 17864 Summary: Increase coverage on admin pages 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: mtompset(a)hotmail.com QA Contact: gmcharlt(a)gmail.com Bug 17793 corrects tabs visible in the search area. These tests will check those. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 17855] New: Updated Koha web installer and new onboarding tool feature to guide users through setting up Koha
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '17

31 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17855 Bug ID: 17855 Summary: Updated Koha web installer and new onboarding tool feature to guide users through setting up Koha Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Updated the Koha web installer so that it has two setup modes: Basic and Advanced. The basic mode limits the control the user has over the data they choose to install into the database. They can only choose whether to install optional data; all default data is installed by default. The advanced mode gives the user greater control to choose whether or not to install default AND optional data. After the web installer has finished the user is redirected to the onboarding tool (with no authentication required in between). In the onboarding tool they create a: Library, Patron category Item type (if they were not installed in the web installer), In addition to always creating a: Patron (which has super librarian privileges which the user will use to log into Koha with) Circulation rule Then the user is redirected to a login page where they login using the patron they just created. If they entered the correct patron account credentials the Koha homepage will appear, and the user can start using Koha as intended due to all necessary data being installed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 322

[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