Tracker Timestamp Problem
Hi all. First post yay.
Anyway, we're eager to use the tracker feature in our organisation but I've run into problems with the new date only field. One problem is I can't get a blank by default, even with the 0 option, but that isn't my main problem.
I have another mandetory date field that when viewed displays correctly, but the unix timestamp when converted is the previous days date. I checked this by outputting the non formatted timestamp after the formatted one and converting the timestamp:
{if $cur_field.type eq 'f' or $cur_field.type eq 'F' or $cur_field.type eq 'j'} {if $cur_field.value}{$cur_field.value|tiki_long_date} Debug:{$cur_field.value}{/if}
For example, the timestamp can be 1206486000 which is 25th March 2008, but the view tracker item will display 26th March 2008.
If I go to the edit section the combo boxes show yesterdays date correctly. If I save it, then it will save the previous days timestamp.
{html_select_date prefix="ins_"|cat:$cur_field.id start_year="-4" end_year="+4" time=$cur_field.value} Debug: {$cur_field.value}
Basically something funny is going on with times, everything appears to be displaying the date correctly even though the timestamp is wrong, except for the edit date combo box which is displaying the correct date but saving wrong.
Anyone know what's going on?