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

[Bug 17494] New: Koha generating duplicate self registration tokens
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '17

02 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17494 Bug ID: 17494 Summary: Koha generating duplicate self registration tokens 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We have reports of patrons receiving the same verification token. I believe this is because we are passing md5_hex a hashref and not a string. I believe what is getting summed is no the patron data, but the memory address that points to the patron hash! We need to stringify the patron hash before passing it to md5_hex. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 17626] New: INSTALL files are outdated
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '17

01 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17626 Bug ID: 17626 Summary: INSTALL files are outdated Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Developer documentation Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Since we are pretty bad to maintain INSTALL files, I'd suggest to point to the wiki. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 16929] New: Wrapper around CSRF call?
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '17

31 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16929 Bug ID: 16929 Summary: Wrapper around CSRF call? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 50

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

[Bug 17513] New: koha-create does not set GRANTS correctly
by bugzilla-daemon＠bugs.koha-community.org 29 Jan '17

29 Jan '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17513 Bug ID: 17513 Summary: koha-create does not set GRANTS correctly Change sponsored?: --- Product: Koha Version: unspecified 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 There is a behavior change between MySQL and MariaDB: With: CREATE DATABASE koha_kohadev; CREATE USER koha_kohadev@localhost IDENTIFIED BY 'password'; CREATE USER koha_kohadev@'%' IDENTIFIED BY 'password'; GRANT ALL PRIVILEGES ON koha_kohadev.* TO koha_kohadev; Using Mysql, as admin user: mysql> SHOW GRANTS FOR koha_kohadev@'localhost'; GRANT USAGE ON *.* TO 'koha_kohadev'@'localhost' IDENTIFIED BY PASSWORD '*2470C0C06DEE42FD1618BB99005ADCA2EC9D1E19' mysql> SHOW GRANTS FOR koha_kohadev; GRANT USAGE ON *.* TO 'koha_kohadev'@'%' IDENTIFIED BY PASSWORD '*2470C0C06DEE42FD1618BB99005ADCA2EC9D1E19' GRANT ALL PRIVILEGES ON `koha_kohadev`.* TO 'koha_kohadev'@'%' Using Mysql, as koha_user user: mysql> SHOW GRANTS FOR koha_kohadev@'localhost'; GRANT USAGE ON *.* TO 'koha_kohadev'@'localhost' IDENTIFIED BY PASSWORD <secret> mysql> SHOW GRANTS FOR koha_kohadev; GRANT USAGE ON *.* TO 'koha_kohadev'@'%' IDENTIFIED BY PASSWORD <secret> GRANT ALL PRIVILEGES ON `koha_kohadev`.* TO 'koha_kohadev'@'%' Using MariaDB, as admin user: MariaDB [(none)]> SHOW GRANTS FOR kohaçkohadev@localhost; GRANT USAGE ON *.* TO 'koha_kohadev'@'%' IDENTIFIED BY PASSWORD '*'2470C0C06DEE42FD1618BB99005ADCA2EC9D1E19 MariaDB [(none)]> SHOW GRANTS FOR kohaçkohadev; GRANT USAGE ON *.* TO 'koha_kohadev'@'%' IDENTIFIED BY PASSWORD '*'2470C0C06DEE42FD1618BB99005ADCA2EC9D1E19 GRANT ALL PRIVILEGES ON `koha_kohadev`.* TO 'koha_kohadev'@'%' So all the same so far :) But, Using MariaDB, as koha_user user: MariaDB [(none)]> SHOW GRANTS FOR kohaçkohadev@localhost; GRANT USAGE ON *.* TO 'koha_kohadev'@'%' IDENTIFIED BY PASSWORD '*'2470C0C06DEE42FD1618BB99005ADCA2EC9D1E19 MariaDB [(none)]> SHOW GRANTS FOR kohaçkohadev; ERROR 1044 (42000): Access denied for user 'koha_kohadev'@'localhost' to database 'mysql' BOOM! The installer does not parse the expected output and then raise an error. -- You are receiving this mail because: You are watching all bug changes.

1 17