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

[Bug 16115] New: JavaScript error on item search form
by bugzilla-daemon＠bugs.koha-community.org 22 Feb '17

22 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16115 Bug ID: 16115 Summary: JavaScript error on item search form Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/catalogue/itemsearch.pl OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org In the template for the item search page there is this at line 290: { 'type': 'select', 'values': [% notforloans.json %] }, [% notforloans.json %] appears to be undefined, whether the search form has been submitted or not. Viewing source shows this: { 'type': 'select', 'values': }, ...and the Firebug console reports this error: SyntaxError: expected expression, got '}' /cgi-bin/koha/catalogue/itemsearch.pl Line 240 -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 16018] New: merges not modifying biblios properly
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '17

20 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16018 Bug ID: 16018 Summary: merges not modifying biblios properly Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: remi.mayrand-provencher(a)inLibro.com Reporter: remi.mayrand-provencher(a)inLibro.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl As the summary says, merges are not modifying biblios properly. Test plan to reproduce the bug: 1)Go to authority, search for anything 2)Click merge on two authorities of the same type that are used at least one time 3)Validate which subfields are corresponding to each authorities in the biblios that uses them 4)Do the whole merge process 5)Validate that the biblios are updated properly (which they are not according to my tests. -- You are receiving this mail because: You are watching all bug changes.

1 50

[Bug 15816] New: Timeout login redirects to home page
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '17

19 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15816 Bug ID: 15816 Summary: Timeout login redirects to home page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P3 Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: library(a)stas.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com On the staff client, when the session times out, or the user is asked to login again, the login always redirects to the home page. Formerly (as of 3.18.6 from which we upgraded to 3.22.1), it would redirect back to the page requested. --------- Example of former behavior: Login has timed out. User clicks link for a new biblio record from z39.50 (Cataloging). Pop-up search window opens, but asks for a login. Once logged in the z39.50 search form is shown. Example of present behavior: Login has timed out. User clicks link for a new biblio record from z39.50 (Cataloging). Pop-up search window opens, but asks for a login. Once logged in the staff home page is shown in the pop-up window. Behavior is the same for other pages as well. It seems the requested page (which appears in the address bar) is not passed to the login form (which is in mainpage.pl) and instead mainpage.pl is shown. Not a deal breaker, but annoying to have to login from scratch (or in another window) to a continue working on a record you were working on yesterday, or continue a session. I suspect Bug 15005. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 16035] New: MARC framework Export misbehaving
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '17

14 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16035 Bug ID: 16035 Summary: MARC framework Export misbehaving Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleishaamohia(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 48910 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=48910&action=ed… more than one file type selection The MARC bibliographic framework Export is misbehaving for Default framework only 1) File will always export as an .ods file regardless of what file type you have selected 2) The first time that you click the Export button and choose a different file type other than CSV then click Cancel will be fine. Then, without refreshing the page, click Export for the same framework again and notice CSV radio selection is checked and stays checked when you select other file types. (See screenshot) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 16529] New: Clean up and improve upload template
by bugzilla-daemon＠bugs.koha-community.org 14 Feb '17

14 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16529 Bug ID: 16529 Summary: Clean up and improve upload template Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/tools/upload.pl OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org The file upload template has a few issues to be fixed: - use of 'onclick' should be corrected - markup errors should be fixed - layout should be adjusted based on whether the page is displaying in a popup or not. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 16387] New: Incorrect loan period calculation when using decreaseLoanHighHolds feature
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '17

09 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16387 Bug ID: 16387 Summary: Incorrect loan period calculation when using decreaseLoanHighHolds feature 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: 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 a loan period is shortened due to using decreaseLoanHighHolds* the time is always set to the current time in X days, even if the original loan period is given in days and not in hours. It should default to 23:59 as is normal for loan periods given in days. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 15822] New: STAFF Advanced search error date utils
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '17

06 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15822 Bug ID: 15822 Summary: STAFF Advanced search error date utils Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: hblancoca(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When i try to search in staff advanced search "topographic signature" 340.11, appears following error: Can't locate object method "ymd" via package "dateonly" (perhaps you forgot to load "dateonly"?) at /usr/share/koha/lib/Koha/DateUtils.pm line 223. the search string is: http://catalogo.edu.co:8080/cgi-bin/koha/catalogue/search.pl?idx=callnum&q=… I can probe, that when i search with "Explorar índices" option enabled the string changes(adding scan variable) and try other values to explore. http://catalogo.edu.co:8080/cgi-bin/koha/catalogue/search.pl?idx=callnum&q=… Really appreciate your help -- You are receiving this mail because: You are watching all bug changes.

1 33

[Bug 15714] New: Remove zebra.log from debian scripts
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '17

30 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15714 Bug ID: 15714 Summary: Remove zebra.log from debian scripts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Scripts koha-start-zebra (as well as koha-stop-zebra) refer to zebra.log. But they also use zebra-output.log and zebra-error.log. The scripts do not correctly use the stdout, stderr and output options from daemon. Either you use output (for both) or you use stdout and stderr. Patch forthcoming. Will also make it possible to add log level "log" to zebrasrv -v to include requests in the zebra-output.log (optionally via koha-conf). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 15889] New: Login with LDAP deletes extended attributes
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '17

30 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15889 Bug ID: 15889 Summary: Login with LDAP deletes extended attributes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: alex.arnaud(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Authentication on Koha using LDAP deletes all *non-mapped* extended attributes. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 16376] New: Koha::Calendar->is_holiday date truncation creates fatal errors for TZ America/Santiago
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '17

29 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16376 Bug ID: 16376 Summary: Koha::Calendar->is_holiday date truncation creates fatal errors for TZ America/Santiago Change sponsored?: --- Product: Koha Version: 3.20 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Koha::Calendar->is_holiday calls the following DateTime truncate method: $localdt->truncate( to => 'day' ); This will truncate 2015-09-06 12:00:00 down to 2015-09-06 00:00:00. This causes major problems in Santiago, Chile, because 2015-09-06 is an invalid local time due to DST. I can't explain why it's a problem in 2015 because DST is weird in Chile in 2015, but it's obviously a problem for every other year as well: http://www.timeanddate.com/time/change/chile/santiago?year=2015 Consider 2014: 2014 Sunday, 27 April, 12:00 Midnight Sunday, 7 September, 12:00 Midnight You shouldn't have a problem on 27 April, because when 27 April 12:00 midnight hits (relative to UTC), local time is changed to 27 April 11:00pm. While UTC marches on, local time has been magically moved back an hour. You will have a problem on 7 September 12:00 midnight though, because that time doesn't exist. As soon as we roll over from 6 September 11:59pm to the next minute... we're actually on to 7 September 01:00:00am. Midnight doesn't exist on that day, which creates the following error in DateTime.pm: "Invalid local time for date in time zone: America/Santiago" This is a problem that the DateTime writer predicted. You can see their comments here: http://cpansearch.perl.org/src/DROLSKY/DateTime-1.26/lib/DateTime.pm https://rt.cpan.org/Public/Bug/Display.html?id=93347 We should probably do something like: eval { $dt->truncate(to => 'day'); } || warn "Eval failed with '$@'\n"; Why are we even doing this day truncation? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41