Roundup Tracker - Issues

Issue 1013097

classification
TimeZone not (reverse) applied on user submitted values
Type: Severity: normal
Components: Web interface Versions:
process
Status: closed fixed
:
: richard : richard, syrk
Priority: normal :

Created on 2004-08-20 19:58 by syrk, last changed 2004-10-08 00:54 by richard.

Messages
msg1431 Author: [hidden] (syrk) Date: 2004-08-20 19:58
I have an editable date in my issue.item.html file
which is _always_ updated by roundup upon submit even
if the textfield is left untouched.

Since the value in the DB is stored as UTC but
displayed in the local timezone, you can't take back
that displayed value and just stuff it back in the DB.
 tried to figure where this is happening, but i can't
see it in the code.. sorry.
msg1432 Author: [hidden] (anonymous) Date: 2004-09-24 09:06
Logged In: NO 

The local timezone offset is added twice on date fields:
- when going from input field to db storage
- when going from db storage to web display

This results in datetime entries autoincrementing by 2x the
local timezone offset on each edit of an issue.

Local timezone offset should be _substracted_ from the input
value when storing into the db, not added.

When I enter a new deadline through the input field::
2004-09-25

my database says::
>>> db.project.get(8,'deadline')
<Date 2004-09-25.02:00:0.000000>

which displays in the web interface as::
2004-09-25.04:00:00 
msg1433 Author: [hidden] (richard) Date: 2004-10-08 00:54
Logged In: YES 
user_id=6405

I have modified the input parser to apply the timezone in the 
correct direction. 
 
History
Date User Action Args
2004-08-20 19:58:00syrkcreate