@hpvd opened this Issue on January 17th 2014

Take year into account by calculation of time to task...

Otherwise these things could happen:

  • tasks from last year were shown
  • time calculation results are wrong

please see attachment

screenshot was taken on January 17th, 2014

@hpvd commented on January 17th 2014
@hpvd commented on January 24th 2014
@tsteur commented on January 24th 2014 Member

In 89452456103674637c863e38e461946a45a53a41: refs #4540 fix time ago is not correct calculated if numberOfSeconds is negative

@tsteur commented on January 24th 2014 Member

Time calculation is fixed.

I think it is intended to show previous tasks as it basically means they were not executed since then (but maybe should) and it helps you to discover this. Maybe I am wrong @matt? Please reopen if we should not show tasks from past

@hpvd commented on January 24th 2014

just updated to TasksTimetable v0.1.2 but it seems to be not completely fixed:

example (please see also attachment):

Scheduled Tasks
The following tasks are scheduled to be executed based on the current server time Friday 24 January 2014 09:04:13.

GeoIPAutoUpdater.update Wednesday 18 December 2013 00:00:46

(in 327 days -8746 hours)

=> time is still calculated wrong
=> maybe one should ad another text and position for "in" in front if the last run was in the past: e.g.: "ago" at the end

(IN XXX days -YYYYY hours)
(XXX days -yyyyyy hours AGO)

@tsteur commented on January 26th 2014 Member

It is fixed in Piwik core, not in the plugin itself. Meaning you will see the fix with the next Piwik release.

This Issue was closed on January 26th 2014
Powered by GitHub Issue Mirror