Zope Timezones Fixed

I finally got around to fixing the timezones for the Zope server. I’ve done this before for other servers, but hadn’t for the personal one, for some reason.

Kudos to Andrew Milton for responding to my query to the OzZope mailing list last year explaining how:

Zope DateTime sucks.

It's looking for 'AEST' for Australian Eastern Standard Time, which as far asI know is only ever used under Windows to represent Australia timezones.

The "workaround" is this;

You need to edit ${ZOPEHOME}/lib/python/DateTime/DateTime.py

You will see a variable called _zmap and the first timezone is 'aest'change it to 'est' , change 'aedt' to 'edt' and find the US 'est' and change it to 'usest'.

You should be fine after that.

I should make this into a MonkeyPatch product.

| I really hope I'm just being an idiot.

It's been broken for 10 years, it's not you that's the idiot.

-- Andrew Milton

Related posts:

1. Zope Uber-Security I *think* I’ve correctly enabled comments now. Zope’s security model...
2. Plone: Why is portal_actions visible in folder_contents? It’s possible that you might come across this in your...
3. Nokia Sucks: A Rant About Timezones I have a Nokia N95 mobile phone. I’ve generally liked...
4. TurboGears: First Impressions TurboGears is my first choice for a new webapp platform,...
5. Bold Steps Ahead I’ve been contemplating moving away from Zope 2 as a...