Inconsistencies in milestone date format

[rangoy]

Symptom:

All milestones appear as 01/01/1970

Problem:

In my installation milestones are saved as unix time (seconds), not microseconds. The time (unix time) is divided by 1000000, and it appears as 1970.

I do not know if it has anything to do with my installation; but my there shouldn't be much special with my installation.

I use trac 0.11.1 combined with the zipped tracjsganttplugin (0.4) found on the wiki page.

Trac installation:

0.11.1

Python: 	2.6.2 (release26-maint, Apr 19 2009, 02:11:59) [GCC 4.3.3]
setuptools: 	0.6c9
SQLite: 	3.6.10
pysqlite: 	2.5.0
Genshi: 	0.5.1
mod_python: 	3.3.1
Pygments: 	0.10
GIT: 	        1.6.0.4
jQuery:	        1.2.6

[R-J]

Seeing the same thing happen here: milestones having a start- and end-date at 1/1/1970 Only one thing is different. This only happens for have a milestones that have a due date set.

I'm using a similar setup. It's a shared host, I can't use easy install. (I created the egg file on a windows-pc, the ssh server doesn't have python 2.6 yet.)

Server running: Ubuntu linux
TracJsGanttPlugin: v0.7 

Trac:		0.11.7
Python:		2.6.5 (r265:79063, Apr 16 2010, 14:15:55) [GCC 4.4.3]
setuptools:	0.6
SQLite:		3.6.22
pysqlite:	2.5.5
Genshi:		0.5.1
mod_python:	3.3.1
Pygments:	1.2.2

trac.ini

[ticket-custom]
...
userstart = text
userfinish = text


[trac-jsgantt]
# Custom fields for start and due dates
fields.start = userstart
fields.finish = userfinish

No errors in the error-log

[Ryan J Ollos]

Replying to rangoy:

In my installation milestones are saved as unix time (seconds), not microseconds. The time (unix time) is diveded by 1000000, and it appears as 1970.

I do not know if it has anything to do with my installation; but my there shouldn't be much special with my installation.

Trac 0.11 stores timestamps in seconds. Trac 0.12 stores them in microseconds.

#8959 is a duplicate, but there is a patch in that ticket.