6.0.0-git
2019-03-18

[#514] nag tasks in kronolith
Summary nag tasks in kronolith
Queue Kronolith
Queue Version HEAD
Type Bug
State Resolved
Priority 1. Low
Owners Horde Developers (at) , jan (at) horde (dot) org
Requester vilius (at) lnk (dot) lt
Created 2004-08-30 (5313 days ago)
Due
Updated 2005-04-26 (5074 days ago)
Assigned 2005-01-11 (5179 days ago)
Resolved 2005-04-22 (5078 days ago)
Milestone
Patch No

History
2005-04-26 09:38:31 vilius (at) lnk (dot) lt Comment #14 Reply to this comment
Confirmed as fixed. Thanks.
2005-04-22 13:32:40 Jan Schneider Comment #13
State ⇒ Resolved
Reply to this comment
This should be fixed in CVS and 2.0.3 now.
2005-01-11 18:24:32 Jan Schneider State ⇒ Assigned
Assigned to Horde DevelopersHorde Developers
 
2005-01-04 13:40:43 vilius (at) lnk (dot) lt Comment #12 Reply to this comment
I found something today, regarding this little problem.



It seems that mktime() function in

http://cvs.horde.org/co.php/kronolith/lib/Kronolith.php?r=1.264#279

http://cvs.horde.org/co.php/kronolith/lib/Kronolith.php?r=1.264#280

and other places in DayView.php, Day.php, etc.

on 1970 01 01 returns negative unix timestamp (-10800).



I _think_ that this is somehow linked with my timezone (EEST or GMT+2) 
because if I try to change first value in mktime from 0 to 3 
everything works as expected.



I'm runing PHP 4.3.2 on Redhat Enterprise Linux 3.0 (U4)
2005-01-03 11:11:37 vilius (at) lnk (dot) lt Comment #11 Reply to this comment
I don't had time to do this yet. But I will try to look at it this week.
2005-01-03 09:35:01 Jan Schneider Comment #10 Reply to this comment
Have you been able to find out why/where this happens?
2004-11-21 11:27:08 Jan Schneider Comment #9 Reply to this comment
I guess you need to track it down yourself then.
2004-11-21 00:47:15 vilius (at) lnk (dot) lt Comment #8 Reply to this comment
I still can.
2004-11-19 23:46:12 Jan Schneider Comment #7
State ⇒ Feedback
Reply to this comment
I can't reproduce this anymore. You, Vilius?
2004-09-25 09:52:51 vilius (at) lnk (dot) lt Comment #6 Reply to this comment
Yes.
2004-09-24 14:11:48 Chuck Hagenbuch Comment #5
Assigned to Jan Schneider
Taken from Horde DevelopersHorde Developers
Reply to this comment
Giving to Jan since he could reproduce it. Is this still happening?
2004-08-31 08:30:29 Jan Schneider Comment #4 Reply to this comment
I can reproduce it too.
2004-08-31 06:36:15 vilius (at) lnk (dot) lt Comment #3
New Attachment: 1970-1.JPG Download
Reply to this comment
Very strange. Because I have this behaviour on 3 horde accounts. 
Screenshot attached. I'l try to debug this later today.
2004-08-31 02:45:03 Chuck Hagenbuch Comment #2 Reply to this comment
I can't reproduce this, and it makes no sense anyway - we only show 
tasks in Kronolith that *have* a due date. And you can't set a task in 
nag to be "due" sometime without setting a date.
2004-08-30 11:25:21 Jan Schneider State ⇒ Assigned
Assigned to Horde DevelopersHorde Developers
 
2004-08-30 10:57:53 vilius (at) lnk (dot) lt Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ nag tasks in kronolith
Queue ⇒ Kronolith
Reply to this comment
If option "Show due tasks in calendar" is turned on in kronolith, and 
there are nag tasks with no dates set, all these tasks are shown on 
1970-01-01 in calendar.

Saved Queries