Please login or register to participate.
gritsak Sep 15, 2010 02:20 PM
Cyn.In desktop client showing wrong timestamp on posts. Checking site shows correct timestamp. Timezone is the same on desktop and Cyn.In server.
Replies (3)
dhiraj Sep 15, 2010 04:34 PM
The desktop calculates a time difference from server time based on your local desktop time zone, to display it to users.

There are 3 places in where time gets affected:
1. The server time and time zone.
2. Zope's timezone
3. Local timezone setting on your desktop

Typically from the symptoms you're reporting, the server timezone is set to UTC, with correct timezone offset of your actual time zone.'s Zope's default setting is also set to UTC, so it's very possibly assuming that the time reported by the server is at UTC, and marking the stored dates as such. This confuses the desktop to believe that the times coming from the server are at UTC, (even though they aren't) and it adjusts based on your local desktop's timezone. (I could be a bit wrong here, and you may have also hit a timezone conversion bug/problem).

What you need to do is set your zope timezone, (search for the discussions on how to do this) and then verify on a *new* content item that the web interface is still reporting the correct time, and then verify if the desktop starts to show the correct times for your items.

All apologies for this perhaps over-complicated reply - timezones and time can be really confusing when multiple conversions are happening all over the place, like this. ;)
gritsak Sep 20, 2010 06:17 PM
Thanks very much for your help, I'll look into these settings.
gsiak Oct 01, 2010 06:30 PM
I've set server timezone and time to UTC and TZ parameter in Zope to 'Europe/Berlin' (within zopectl). This give the right time in webinterface. But time in client is still with wrong offset of +2h, wich is exactly the difference between local time and UTC, given by timezone in my windows 7. Is there a bug in Desktop Client?