1 balupton Dec 03, 2006 12:55
3 balupton Dec 03, 2006 18:38
Hrmmm... Maybe my server just did dst then, because the time right now should be... 2:30 am, and the time the server is saying is 12:30 am...
Hrmm... We'll see
4 blueyed Dec 03, 2006 19:34
b2evo doesn't know anything about timezones. (which is a shame IMHO)
It only has an offset value (between "local" and server time).
"local" can mean whatever you want it to mean: it's mostly the time in admin land.
5 balupton Dec 03, 2006 19:37
Ok cool, once i get my computer to actually figure out i'm in dst land now, then i'll go set the offset.
Cheers.
You mean b2evo actually did something about dst? Or did it appear to go the wrong way when your server went the right way? My experience has been that I have to go tweak my back office because I live in a state that does not do dst but my server lives in a state that does. Therefore my server offset is an hour out of sync twice a year. When I lived in a state that did dst I never noticed an issue, but it's possible I didn't pay enough attention to notice.