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

[Bug 16094] New: error with mysql enterprise
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '16

06 Sep '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16094 Bug ID: 16094 Summary: error with mysql enterprise Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: hblancoca(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, when i try to modify an user get this error DBIx::Class::Storage::DBI::_dbh_execute(): Incorrect integer value: '' for column 'guarantorid' at row 1 at /usr/share/koha/lib/C4/Members.pm line 665 i review the sorce code <label for="contactname">Nombre de la institución: </label> [% IF ( guarantorid ) %] <span>[% contactname %]</span> <input name="contactname" id="contactname" type="hidden" size="20" value="[% contactname %]" /> [% ELSE %] <input name="contactname" id="contactname" type="text" size="20" value="[% contactname %]" /> [% END %] but when do not exist guarantor, how can i apply 0 (i think)? thansk for your help. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 15819] New: Error when edit borrowers "There are no patron categories defined" but categories exists
by bugzilla-daemon＠bugs.koha-community.org 06 Sep '16

06 Sep '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15819 Bug ID: 15819 Summary: Error when edit borrowers "There are no patron categories defined" but categories exists Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: hblancoca(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com when i try to edit borrower appears "There are no patron categories defined" in memberentry.pl but the categories works fine, i believe that the problem is the variable to .tt aply to cataloging module not appear authorised values I really apreciate your help -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 16070] New: Empty (undef) system preferences may cause some issues in combination with memcache
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '16

28 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16070 Bug ID: 16070 Summary: Empty (undef) system preferences may cause some issues in combination with memcache Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: abl(a)biblos.pk.edu.pl QA Contact: testopia(a)bugs.koha-community.org See Bug 11998 comment #113 -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 15930] New: DataTables patron search defaulting to 'starts_with' and not getting correct parameters to parse multiple word searches
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '16

25 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15930 Bug ID: 15930 Summary: DataTables patron search defaulting to 'starts_with' and not getting correct parameters to parse multiple word searches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org So far I know this is affecting: request.pl svc/members.search When two terms are used to search e.g. 'Henry Acevedo' no results are returned The query in the system is searching for borrower.'surname' LIKE 'Henry Acevedo%' The searchtype parameter needs to e set to 'contain' -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 15700] New: Buttons don't work in inventory/stocktaking
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '16

24 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15700 Bug ID: 15700 Summary: Buttons don't work in inventory/stocktaking Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: aleishaamohia(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org To reproduce: Go to Tools, Inventory/stocktaking Click Submit to show selection of items Buttons 'Mark seen and continue' and 'Continue without marking' do not work. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 15974] New: Rancor - 942c is always displaying first in the list.
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '16

17 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15974 Bug ID: 15974 Summary: Rancor - 942c is always displaying first in the list. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: ed.veal(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When you open a record up using the advanced marc editor if there is a 942c the display will show the first in the list of possible koha Itypes. If you change this to the correct type it will save correctly. However, if you open a record and don't correct the 942c it will save based on what appears in the field (the first option). Ed -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 15929] New: typo in explanation for MaxSearchResultsItemsPerRecordStatusCheck
by bugzilla-daemon＠bugs.koha-community.org 16 Aug '16

16 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15929 Bug ID: 15929 Summary: typo in explanation for MaxSearchResultsItemsPerRecordStatusCheck Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There's a typo in the explanation for the new MaxSearchResultsItemsPerRecordStatusCheck sys pref that was added in 3.22.2. "If a record has more than this number of items, they availability statuses ..." they should be the -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 15782] New: Paging on comments moderation broken
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '16

14 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15782 Bug ID: 15782 Summary: Paging on comments moderation broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When you have more than a "page" of comments already moderated (possibly also with 'to moderate'), a paging option is shown at the bottom. But instead of moving you to the next page, it will move you by one comment entry, which is not the expected behaviour and makes it really hard to use for systems with a lot of comments. Example: a b c d ... Use > to navigate to the next page b c d e ... -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 15809] New: versions of CGI < 4.08 do not have multi_param
by bugzilla-daemon＠bugs.koha-community.org 02 Aug '16

02 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15809 Bug ID: 15809 Summary: versions of CGI < 4.08 do not have multi_param Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal 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 On debian Jessie, the CGI version is >= 4.08 Since this version, the param method raise a warning "CGI::param called in list context". Indeed, it can cause vulnerability if called in list context https://metacpan.org/pod/CGI#Fetching-the-value-or-values-of-a-single-named… http://blog.gerv.net/2014/10/new-class-of-vulnerability-in-perl-web-applica… There is a long journey to get rid of these warnings. First I suggest to redefine the multi_param method when the CGI version installed is < 4.08, it will allow us to move the wrong ->param calls to ->multi_param without waiting for everybody to upgrade. The different ways to call these 2 methods are: my $foo = $cgi->param('foo'); # OK my @foo = $cgi->param('foo'); # NOK, will raise the warning my @foo = $cgi->multi_param('foo'); #OK $template->param( foo => $cgi->param('foo') ); # NOK, will raise the warning and vulnerable $template->param( foo => scalar $cgi->param('foo') ); # OK -- You are receiving this mail because: You are watching all bug changes.

1 42

[Bug 15853] New: Add author and link columns to opac course reserves table
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '16

01 Aug '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15853 Bug ID: 15853 Summary: Add author and link columns to opac course reserves table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To be done: 1 - Add an author column to the opac course reserves table 2 - Add a 'link' column to the opac course reserves table, populated from the 856$u field -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15