Zope 2.6.0 has a bug in DateTime.rfc822(). The bug appears when you are NOT in a DST timezone, causing a "Name Error: Global name localzone is not defined" error. This will affect many parts of your Zope operations, luckily, the fix is simple: - Download the fixed DateTime.py, from http://www.zope.org/Members/regebro/datetime_260_fix - Put the downloaded DateTime.py into the lib/python/DateTime directory, replacing the one that is there. - Restart the server. This fix is ONLY valid for Zope 2.6.0. Earlier versions of Zope does not have this bug, and this fix will be included in any future releases of Zope. Best Regards Lennart Regebro http://www.easypublisher.com/
Is this in CVS? What tag should I snag?
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Lennart Regebro Sent: Sunday, October 27, 2002 2:11 AM To: zope@zope.org Subject: [Zope] Bug in Zope 2.6.0: Fix availiable
Zope 2.6.0 has a bug in DateTime.rfc822(). The bug appears when you are NOT in a DST timezone, causing a "Name Error: Global name localzone is not defined" error.
This will affect many parts of your Zope operations, luckily, the fix is simple: - Download the fixed DateTime.py, from http://www.zope.org/Members/regebro/datetime_260_fix - Put the downloaded DateTime.py into the lib/python/DateTime directory, replacing the one that is there. - Restart the server.
This fix is ONLY valid for Zope 2.6.0. Earlier versions of Zope does not have this bug, and this fix will be included in any future releases of Zope.
Best Regards
Lennart Regebro http://www.easypublisher.com/
From: "Charlie Reiman" <creiman@kefta.com>
Is this in CVS? What tag should I snag?
It's in the CVS as well, yes. The correct tag would be Zope-2_6-branch if I remember correctly. That is the current maintenance branch, if you want any other bugfixes than just this one. Best Regards Lennart Regebro Torped Strategi och Kommunikation AB
participants (2)
-
Charlie Reiman -
Lennart Regebro