[Typo3-dev] BIG problem with timestamp and server at different GMT
stefano cecere
scecere at krur.com
Mon Nov 15 15:04:27 CET 2004
hallo everybody
i think this problem occurs only to people who have a typo3
installation in a different timezone.
i have mine in the States (at -7 hours) and this is the problem:
typo3 by default sets dates/times with timestamp (the kickstarter makes
this, and the whole system seems to be developed (very well, indeed)
upon dates and times in timestamp)
the problem is that i have just "date" fields.
when i edit the date field in a record of mine extension, i put in
"today", or "today + 2", or "10/11/2004".. it works, ok.
but then typo3 records the timestamp version of it.
and when it has to show that date, it's sensitive to the time of the
server..
so, if for example i did enter "10/11/2004", now it can show me
"9/11/2004" !!!
i know that the timezone topic has been (a little) discussed last
year.. but i think it's "time" to take it in serious consideration...
i think the easiest way would be to define a global "timezone" for the
server, and then to add a timezone field to the FE and BE users. with
time, to develop a little class for managing dates.. (at the beginning
it could just return the time() function like it works now) first to
use in the backend, then for extensions.. so that for typo3 4.0 the
whole system and the main extensions will forget the problematic time()
function..
what do you think?
how can i (temporary) solve my problem with wrong dates in the backend?
to move my server here in Milan?
greets
stefano cecere
krur.entertainment
More information about the TYPO3-dev
mailing list