You are not logged in Log in Join
You are here: Home » Download Zope Products » Zope » Zope » Zope 2.2.4 released
Log in
Name

Password

 
Link icon Forgot your password?
Print

Zope 2.2.4 released

Zope 2.2.4 has been released - you can download it from Zope.org:

http://www.zope.org/Products/Zope/2.2.4/

This release supercedes the 2.2.3 release, which had an error that prevented permissions from being acquired correctly. Until the testing infrastructure that has been started in the 2.3 CVS is more mature and there is a useful regression test rig, we'll be planning for at least one (short) beta period for third-dot releases.

This bug-fix release contains the fixes for all released Hotfixes to date, as well as fixes for a memory leak in the Acquisition module, various ZCatalog fixes and a fix for the infamous "__call__" bug. It also contains a fix for a problem in header parsing in the dtml sendmail tag that has affected some users recently. The problem with caching of ImageFile objects (mainly icons in the Zope management interface) in the 2.2.4 beta is also fixed (and verified using the Cacheability Engine (http://www.web-caching.com/cacheability.html).

For more information on what is new in this release, see the CHANGES.txt and HISTORY.txt files for the release:

Note that we have also posted "diff" updates as .tgz files that will let you easily upgrade an existing 2.2.x site. These updates are available for those currently using the 2.2.x source release or the 2.2.x binary releases.

To apply a differential update to your site:

  • download the appropriate .tgz file from zope.org
  • shutdown your Zope process
  • copy the .tgz to your Zope directory and extract it
  • run w_pcgi or wo_pcgi if you are not using a binary release
  • restart your process

Copyright (c) 2011 Zope Foundation. All rights reserved. Legal | Contact
If you can read this text, it means you are not experiencing the Plone design at its best. Plone makes heavy use of CSS, which means it is accessible to any internet browser, but the design needs a standards-compliant browser to look like we intended it. Just so you know ;)