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

[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 17744] New: OAI: oai_dc has no element named dcCollection
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '17

29 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17744 Bug ID: 17744 Summary: OAI: oai_dc has no element named dcCollection Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Web services Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 12252 OAI GetRecord and ListRecords, when called with metadataPrefix=oai_dc, return something like this: <metadata> <oai_dc:dcCollection xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd"> <oai_dc:dc> <oai_dc:title>...</oai_dc:title> ... </oai_dc:dc> </oai_dc:dcCollection> </metadata> According to http://www.openarchives.org/OAI/2.0/oai_dc.xsd there is no dcCollection element in oai_dc. Moreover the OAI Repository Explorer (http://re.cs.uct.ac.za/) returns errors about this: [Error] re.ZeDK9z:3:756: cvc-complex-type.2.4.a: Invalid content was found starting with element 'oai_dc:dcCollection'. One of '{"http://www.openarchives.org/OAI/2.0/oai_dc/":dc}' is expected. Some other OAI harvesting tools also fail to parse the response successfully. I found a discussion about this: https://lists.katipo.co.nz/public/koha/2016-April/045130.html There is a patch provided (https://lists.katipo.co.nz/public/koha/2016-April/045283.html) but no bug was opened. This is a regression caused by bug 12252, and it affects all versions since 3.22 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12252 [Bug 12252] OAI-PMH GetRecord result doesn't include item data -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 17743] New: Item search: indexes build on MARC do not work in item' s search
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '17

29 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17743 Bug ID: 17743 Summary: Item search: indexes build on MARC do not work in item's search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: z.tajoli(a)cineca.it QA Contact: testopia(a)bugs.koha-community.org In Items search(Home › Catalog › Item search ) it is possible to insert personal indexes based on MARC tags and subfields. Those indexes are managed by Item search fields (Home › Administration › Item search fields). But now in master indexes based on 245$c (and others tags like 260, 001, etc.) doesn't work. If I use it, the system doesn't do any filter on data; it list all records with an item. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 17761] New: Renewing or returning item via the checkouts table causes lost and damaged statuses to disappear
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '17

29 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17761 Bug ID: 17761 Summary: Renewing or returning item via the checkouts table causes lost and damaged statuses to disappear 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Due to the fact that the lost and damaged status are contained within the due_due span, when the item is renewed or returned these statuses disappear. Some librarians find this disconcerting and it seems that it would be better to keep the visible. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 17652] New: opac-account.pl does not include login branchcode
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '17

29 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17652 Bug ID: 17652 Summary: opac-account.pl does not include login branchcode 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: chris.kirby(a)ilsleypubliclibrary.org QA Contact: testopia(a)bugs.koha-community.org opac-account.pl does not include login branchcode, whereas the other pages (opac-user, opac-memberentry, opac-passwd, opac-readingrecord, opac-suggestions, opac-messaging, opac-shelves)available to users on login DO provide the login branchode. Having the login branchcode available on opac-account.pl would facilitate customization of the OPAC for individual branches. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 17681] New: Some typos
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '17

29 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17681 Bug ID: 17681 Summary: Some typos Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 17547] New: (MARC21) Chronological term field 648 not indexed
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '17

29 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17547 Bug ID: 17547 Summary: (MARC21) Chronological term field 648 not indexed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Even though the authority search in the OPAC allows searching Chronological term authority records, the 'usage' column is always 0, because searching for linked bibliographical records always returns 0. This is because 648$9 is not being added in the Koha-Auth-Number index -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 17749] New: Missing l in '.pl
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '17

29 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17749 Bug ID: 17749 Summary: Missing l in '.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[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