Dates all wrong?

[SomeoneNew]

Is it me or dates are all wrong? Specially on time zone...

A task had "Today" as deadline, although there was 3 hours and a half for tomorrow still left...
Also the dates are shown all wrong, and when it says for example "saturday" one might think, damn.. THIS saturday!.. But NO, its a saturday within a month.... So, please fix all this.

For what would someone want a task system if times and dates are all wrong.

[Buddha]

Since yopu asked the question...

I think you have the problem, not the code...meaning your software/hardware is jacked up somehow.

[SomeoneNew]

Sorry to break your heart but no, since I tried on 3 servers already.

Oh, so 2 servers are "jacked up" and so is mine?. Well, I should stop paying them and tell them that their software/hardware is jacked up, In case they dont understand what Im talking about, I'll give them your phone number so you can explain them whats a jacked up server!.


:p

If the task is due Tuesday in a week, it will say "Tuesday"... But what if I'm on Monday?, this is the issue.
I'm on Monday 22nd and I put a task for Tuesday 30th, On Deadline I'll see "Tuesday".. and I'll think "heck, due tomorrow!?"... So I have to edit the task to see the actual date. 

[stan]

hmmm yes i noticed that too... the dates are wrong for a couple or a few hours past midnight...
but it never bothered me cause i was working late, and still considered 2am as "today", not "tomorrow".
but i guess i should check it again

[SomeoneNew]

Yes but in this case, theres a week of diference
I put task due to next tuesday, I'm on monday and it says "tuesday"... I'll think its tomorrow...

[stan]

ah ha! well you'd finished your work early then! you'd have a week off!!

[lucasinc]

I think if the task is due tomorrow you'll see tomorrow, if today is it's monday and it says tuesday obviously the task isn't for tomorrow, or it would say tomorrow.

What should that case say? next tuesday? or "tuesday (not tomorrow)"?

[alexej]

I think the problem is that the relative date values (today, tomorrow, etc.) are being set based on UTC, not on the local time zone. I also encounter this problem. The day value changes exactly at 0:00:00 UTC.

[mscroggi]

I only have a local installation of TF so all the UTC and timezone stuff isnt needed..  I am doing some reporting on the tasks comments etc.. but the dates are stored in UTC in the database...   Instead of changing the reporting to adjust the returned timestamp, I decided just to take all the timezone stuff out of the equation.  

It is a relatively simple procedure..  I searched the tree for the gmdate() routine calls and replaced them with date() calls..    gmdate was found in these files:
      
   ./include/classes/tzn_generic.php
   ./include/classes/pkg_project.php
   ./xajax.task.php                
   ./public.php                    
   ./index.php                      
   ./xajax/xajax.inc.php            
   ./print_list.php  

I also set the timezone offset to be zero in config.php -   define('TZN_TZDEFAULT','0');

I also modified all of my existing datestamps in the database to be local times..    (I am GMT -6 hours):

Code:

update frk_itemComment set postDate=date_sub(postDate, interval 6 hour)
update frk_itemComment set lastChangeDate=date_sub(lastChangeDate, interval 6 hour) where DATE(lastChangeDate) > '2009-01-01'

update frk_itemFile set postDate=date_sub(postDate, interval 6 hour)

update frk_itemStatus set statusDate=date_sub(statusDate, interval 6 hour)

update frk_member set lastLoginDate=date_sub(lastLoginDate, interval 6 hour) where DATE(lastLoginDate) > '2009-01-01'
update frk_member set creationDate=date_sub(creationDate, interval 6 hour)
update frk_member set lastChangeDate=date_sub(lastChangeDate, interval 6 hour) where DATE(lastChangeDate) > '2009-01-01'

update frk_projectStatus set statusDate=date_sub(statusDate, interval 6 hour)

Seems to work great..

Hope this helps..