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

[Bug 16714] New: Unexpected logout with "IP address change"
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '19

16 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16714 Bug ID: 16714 Summary: Unexpected logout with "IP address change" 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 I get a new issue (not sure since when) under Plack: I am logged out with "IP address change" just after the first login. To reproduce: - logout - restart plack - login - click somewhere => You will be logged out I have tried to debug: diff --git a/C4/Auth.pm b/C4/Auth.pm index 985bd39..a494ddf 100644 --- a/C4/Auth.pm +++ b/C4/Auth.pm @@ -818,6 +818,9 @@ sub checkauth { $userid = $s_userid; $sessiontype = $session->param('sessiontype') || ''; } + + warn $ip; + warn $ENV{REMOTE_ADDR}; if ( ( $query->param('koha_login_context') && ( $q_userid ne $s_userid ) ) || ( $cas && $query->param('ticket') && !C4::Context->userenv->{'id'} ) || ( $shib && $shib_login && !$logout && !C4::Context->userenv->{'id'} ) I get: After the login: $ip=undef, $ENV{REMOTE_ADDR}=192.168.254.1 After the click producing the logout: $ip=192.168.254.1, $ENV{REMOTE_ADDR}=127.0.0.1 After the second login: $ip=127.0.0.1, $ENV{REMOTE_ADDR}=127.0.0.1 -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 16765] New: Subject links in XSLT detail display do not break into subdivisions
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '19

12 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16765 Bug ID: 16765 Summary: Subject links in XSLT detail display do not break into subdivisions Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: Boze.1(a)nd.edu QA Contact: testopia(a)bugs.koha-community.org Created attachment 52501 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=52501&action=ed… Illustration of the difference between XSLT and non-XSLT subject links Version: 3.22.04.000 Also tested on older versions and 16.05.00.000 (Catalyst demo site) Using the non-XSLT detail display, subject links are broken up into increasingly detailed subdivisions that can be clicked on. In the attached image, you can see in the first three screen captures that each subject subdivision is a separate link, and creates a search at that level of the subject. It also conveniently provides a tooltip that shows which MARC subfield the subdivision is coming from. The fourth screen capture shows what happens when the XSLT display is in effect. The entire subject with all subfields are treated as a single search. The subfields cannot be searched separately. Note the the same behavior applies to the links for additional authors. It would be great to have the XSLT option work the same way as the non-XSLT option. Settings for screen capture 4 (in attachment) OPACXSLTDetailsDisplay = default TraceSubjectSubdivisions = Include Settings for screen capture 1-3 (in attachment) OPACXSLTDetailsDisplay = (empty, no XSLT) TraceSubjectSubdivisions = Include -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 16905] New: item modification by age display screwy
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '19

11 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16905 Bug ID: 16905 Summary: item modification by age display screwy Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 53315 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=53315&action=ed… large See attached. On big screens the rule number is under the buttons -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 16521] New: <<item.*>> and <<biblio.*>> not expanding on DUE, PREDUE notices.
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '19

10 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16521 Bug ID: 16521 Summary: <<item.*>> and <<biblio.*>> not expanding on DUE, PREDUE notices. Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Items, Biblio and issues information should be available on DUE and PREDUE notices, but are not populated. I believe that this is a regression. To reproduce: Prerequisites: System set up to run predue notices. 1/ Create DUE and PREDUE letters with the following content for email: The following item is due: <<biblio.title>>, (<<item.barcode>>), <<issues.date_due>> 2/ Check out two items, and back-date the date due so that one will generate a predue notice, and the other is due today. 3/ Run advanced_notices.pl Note that the item information in each notice will show as , (), -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 16796] New: Patron categories: Crash if enrolment date is not valid
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '19

10 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16796 Bug ID: 16796 Summary: Patron categories: Crash if enrolment date is not valid Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org To reproduce: - Create or edit a patron category - Leve enrolment period empty - Manually enter wrong enrolment date, e.g. 99/99/2016 and save. Result: Software error: The 'day' parameter ("99") to DateTime::new did not pass the 'an integer which is a possible valid day of month' callback at /usr/lib/perl5/DateTime.pm line 199 DateTime::new(undef, 'hour', 0, 'minute', 0, 'second', 0, 'month', 06, ...) called at /usr/share/kohaclone/Koha/DateUtils.pm line 172 Koha::DateUtils::dt_from_string(99.06.2016) called at /usr/share/kohaclone/admin/categories.pl line 98 -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 16931] New: advanted search with "all" in location and library filters return nothing
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '19

10 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16931 Bug ID: 16931 Summary: advanted search with "all" in location and library filters return nothing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: morgane.alonso(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 16333] New: Google Calendar integration don't work
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '19

07 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16333 Bug ID: 16333 Summary: Google Calendar integration don't work Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: wosch(a)freebsd.org On the page https://koha-community.org/calendar/ is a link 'g+ Add to Google'. I tried it out and google calendar reports an error message: "This email address isn't associated with an active Google Calendar account: https://koha-community.org/?plugin=all-in-one-event-calendar&controller…. Please check the email address and try again." -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 16347] New: many news articles are tagged excessively or not tagged at all
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '19

07 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16347 Bug ID: 16347 Summary: many news articles are tagged excessively or not tagged at all Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: mirko(a)abunchofthings.net The usage of categories in news posts is weird. The Koha newsletter seems to be using every category available, while 3.22 is not tagged at all. https://koha-community.org/category/release/ has mostly 3.20. Where is 3.22? Why are all the community newsletters showing up there? https://koha-community.org/category/release/3-22/ has newsletters almost exclusively. 3.22.1 is the last one listed. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 16840] New: URLs for old releases are broken with every new release
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '19

07 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16840 Bug ID: 16840 Summary: URLs for old releases are broken with every new release Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: jsn.sherman(a)gmail.com I'm working up a nice CentOS 7 ansible role that builds Koha from the tarball release. The way you shuffle tarball upon release makes automating koha builds more difficult than it has to be, and is user hostile. When you move tarballs under old releases, you don't offer a redirect to the new location, instead you return a 404. When you publish content to the web, you should treat that URL as valid for as long as you have the associated content. In this case, you still have the content, and you know exactly where it is. Ideally, you would offer clients a 301 redirect to the new location. You should only return a 404 when you deleted content or honestly have no idea what the client is asking for. This is a general website stewardship issue, and it may not seem like the most critical thing when you are trying to get a release out the door, so I would be happy to contribute my expertise and/or time to improve this aspect of release management for Koha. Thanks! -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 16743] New: Datatables error when checking overdues in chrome
by bugzilla-daemon＠bugs.koha-community.org 05 Feb '19

05 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16743 Bug ID: 16743 Summary: Datatables error when checking overdues in chrome Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: james.elian(a)britishschool.ro QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 52410 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=52410&action=ed… Screenshot of error This error does not occur in Firefox or Internet Explorer, only in Chrome. On going to a patron page when the patron has overdue items, no items show in the checkout table. If "Always show checkouts immediately" is checked, an error message appears. A screenshot is here as an attachment, and the text is: "DataTables warning: table id=issues-table - Cannot reinitialise DataTable. For more information about this error, please see http://datatables.net/tn/3" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3