[Koha-bugs] [Bug 14036] New: "Date::Calc::Add_Delta_YM(): not a valid date" error when accessing subscription detail

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14036

            Bug ID: 14036
           Summary: "Date::Calc::Add_Delta_YM(): not a valid date" error
                    when accessing subscription detail
 Change sponsored?: ---
           Product: Koha
           Version: 3.18
          Hardware: All
                OS: All
            Status: NEW
          Severity: major
          Priority: P5 - low
         Component: Serials
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: rolando.isidoro at gmail.com
        QA Contact: testopia at bugs.koha-community.org
                CC: colin.campbell at ptfs-europe.com

When accessing the subscription detail page for a serial with unknown "Planned
date" and/or "Published date" the following error occurs:

subscription-detail.pl: Date::Calc::PP::Add_Delta_YM():
Date::Calc::Add_Delta_YM(): not a valid date at
/usr/share/koha/lib/C4/Serials.pm line 2607
 at /usr/share/perl/5.14/CGI/Carp.pm line 379
    CGI::Carp::realdie('[Tue Apr 21 14:43:06 2015] subscription-detail.pl:
Date::Calc...') called at /usr/share/perl/5.14/CGI/Carp.pm line 475
    CGI::Carp::die('Date::Calc::PP::Add_Delta_YM(): Date::Calc::Add_Delta_YM():
n...') called at /usr/share/perl5/Carp/Clan.pm line 225
    Carp::Clan::__ANON__('Date::Calc::Add_Delta_YM(): not a valid date') called
at /usr/share/perl5/Date/Calc/PP.pm line 408
    Date::Calc::PP::DATECALC_DATE_ERROR('Add_Delta_YM') called at
/usr/share/perl5/Date/Calc/PP.pm line 817
    Date::Calc::PP::Add_Delta_YM(0000, 00, 00, 0, 1) called at
/usr/share/koha/lib/C4/Serials.pm line 2607
    C4::Serials::GetNextDate('HASH(0x6244de0)', '0000-00-00') called at
/usr/share/koha/lib/C4/Serials.pm line 2382
    C4::Serials::abouttoexpire(525) called at
/usr/share/koha/intranet/cgi-bin/serials/subscription-detail.pl line 104

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.