[ic] time tag with adjust in February bug?

[Mike Heins]

Quoting Peter (peter at pajamian.dhs.org):
> On 04/01/2013 12:08 PM, Peter wrote:
> >On 04/01/2013 03:27 AM, Paul Jordan wrote:
> >>
> >>Doing this today:
> >>
> >>A)    [time]%c[/time] <br />
> >>B) - 1d: [time adjust='-1 day']%c[/time] <br />
> >>C) - 1m1d: [time adjust='-1 month 1 day']%c[/time] <br />
> >>D) - 2m1d: [time  adjust='-2 month 1 day']%c[/time] <br />
> >>
> >>gives me:
> >>
> >>A)                Sun Mar 31 07:04:42 2013
> >>B) - 1d:        Sat Mar 30 07:04:42 2013
> >>C) - 1m1d:   Sat Mar 2 06:04:42 2013
> >>D) - 2m1d:   Wed Jan 30 06:04:42 2013
> >
> >Is your version of Interchange from before or after May of 2009? The
> >time adjustment code was completely rewritten then.
> 
> Anyways, after further (off-list) discussion, the server is running
> the newer time adjustment code.  having looked through the
> adjust_time function again nothing jumps out at me that could cause
> this.  I would need to debug on the server to make sure that the
> correct values are being passed to mktime().  If so then it's going
> to be an issue with POSIX::mktime().

There is no "month". 1m is one minute, the "onth" makes no difference.
And you can't do addition and subtraction by combining terms...

This is April Fool's on European time, no?
-- 
Mike Heins
Perusion -- Expert Interchange Consulting    http://www.perusion.com/
phone +1.765.253.4194  <mike at perusion.com>

Few blame themselves until they have exhausted all other possibilities.
 -- anonymous