I've just installed Plone 2.5.1 on Zope 2.9.6 running on FreeBSD 6-STABLE. On my newly created Plone site, whenever I add an event, it's displayed with the wrong time. For instanced, if I create one that runs between 2006-12-05 19:30 and 22:00, it gets rendered like: (<span class="location">Some Event</span>, from <abbr class="dtstart" title="2006-12-05 19:30:00">2006-12-05 13:30</abbr> to <abbr class="dtend" title="2006-12-05 22:00:00">2006-12-05 16:00</abbr>) The server and I live in the CST time zone, which accounts for the 6-hour offset (as though I entered the time in UTC and it's converting it to CST for display). But since I never entered a timezone anywhere, why's it doing any conversion at all instead of just assuming that all times entered are local to the server? Is there a way to fix this, other than deliberately entering all times for events six hours too late, and letting Plone "fix" the display? -- Kirk Strauser Daycos
Kirk Strauser wrote at 2006-12-3 12:19 -0600:
I've just installed Plone 2.5.1 on Zope 2.9.6 running on FreeBSD 6-STABLE. On my newly created Plone site, whenever I add an event, it's displayed with the wrong time. For instanced, if I create one that runs between 2006-12-05 19:30 and 22:00, it gets rendered like:
(<span class="location">Some Event</span>, from <abbr class="dtstart" title="2006-12-05 19:30:00">2006-12-05 13:30</abbr> to <abbr class="dtend" title="2006-12-05 22:00:00">2006-12-05 16:00</abbr>)
The server and I live in the CST time zone, which accounts for the 6-hour offset (as though I entered the time in UTC and it's converting it to CST for display). But since I never entered a timezone anywhere, why's it doing any conversion at all instead of just assuming that all times entered are local to the server? Is there a way to fix this, other than deliberately entering all times for events six hours too late, and letting Plone "fix" the display?
It might have to do with how you entered the date. Watch out this example: >>> DateTime('2006-12-05 13:30:00') DateTime('2006/12/05 13:30:00 GMT+1') >>> DateTime('2006-12-05T13:30:00') DateTime('2006/12/05 13:30:00 GMT+0') This means that a single character (the "T" above) may change the timezone the date is assumed to come from.
-- Kirk Strauser Daycos
-- Dieter
On Monday 04 December 2006 12:32, Dieter Maurer wrote:
It might have to do with how you entered the date.
Watch out this example: >>> DateTime('2006-12-05 13:30:00')
DateTime('2006/12/05 13:30:00 GMT+1')
>>> DateTime('2006-12-05T13:30:00')
DateTime('2006/12/05 13:30:00 GMT+0')
This means that a single character (the "T" above) may change the timezone the date is assumed to come from.
Interesting! However, I entered the date via the widget on the "add an event" form - no typing was necessary (or even possible). That leads me to believe that this is a deliberate feature in Plone, or a bug in my installation. -- Kirk Strauser Daycos
Just for the record, for a solution look at ticket #5987 on dev.plone.org Kirk opened: http://dev.plone.org/plone/ticket/5987 In short: the reason of dates misbihaviour is a change in Zope 2.9.6. Just use Zope 2.9.5 till the problem is solved in Plone.
participants (3)
-
Dieter Maurer -
Kirk Strauser -
libraM