6.0.0-RC7
6/27/26

[#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 8/30/04 (7971 days ago)
Due
Updated 4/26/05 (7732 days ago)
Assigned 1/11/05 (7837 days ago)
Resolved 4/22/05 (7736 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
319 vilius (at) lnk (dot) lt Comment #14 Reply to this comment
Confirmed as fixed. Thanks.
401 Jan Schneider Comment #13
State ⇒ Resolved
Reply to this comment
This should be fixed in CVS and 2.0.3 now.
326 Jan Schneider Assigned to Horde DevelopersHorde Developers
State ⇒ Assigned
 
431 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)
3711 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.
19 Jan Schneider Comment #10 Reply to this comment
Have you been able to find out why/where this happens?
811 Jan Schneider Comment #9 Reply to this comment
I guess you need to track it down yourself then.
1512 vilius (at) lnk (dot) lt Comment #8 Reply to this comment
I still can.
1211 Jan Schneider Comment #7
State ⇒ Feedback
Reply to this comment
I can't reproduce this anymore. You, Vilius?
519 vilius (at) lnk (dot) lt Comment #6 Reply to this comment
Yes.
482 Chuck Hagenbuch Comment #5
Taken from Horde DevelopersHorde Developers
Assigned to Jan Schneider
Reply to this comment
Giving to Jan since he could reproduce it. Is this still happening?
298 Jan Schneider Comment #4 Reply to this comment
I can reproduce it too.
156 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.
32 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.
2111 Jan Schneider Assigned to Horde DevelopersHorde Developers
State ⇒ Assigned
 
5310 vilius (at) lnk (dot) lt Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ nag tasks in kronolith
Queue ⇒ Kronolith
State ⇒ Unconfirmed
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