CMFDeployment 1.1.0b1 (Beta release) (Jul 05, 2006)

This is not a final release. Experimental releases should only be used for testing and development. Do not use these on production sites, and make sure you have proper backups before installing.

The next release of the 1.1 development line. This release is for Plone 2.0-2.1, it adds compatibility with Zope 2.9, better cross platform support (windows), and some bug fixes.

For additional information about this project, please visit the overview page .

Available downloads

Change log

Full Changelog since last release

------------------------------------------------------------------------
r1407 | hazmat | 2006-06-29 23:47:46 -0700 (Thu, 29 Jun 2006) | 8 lines


   in allowing for functions to be utilized during rendering process (for ical event renditions )
   non skin methods were broken. a new syntax for utilizing functions has been introduced
   via the TALES accessible function deploy.bind( func, *args, **kw) which creates a curried/
   bound function. object methods can be directly utilized again, and backwards compatiblity
   for existing rendering functions has been implemented till we can stamp xml config w/
   version info and upgrade configuration (1.2).

------------------------------------------------------------------------
r1398 | hazmat | 2006-06-27 12:02:51 -0700 (Tue, 27 Jun 2006) | 20 lines

 - zope 2.9 compatiblity, previously cmfd was depending on overriding manage_afteradd
   to avoid double method invocation when the constructed policy was attached to
   the tool, the new ofs.events mechanism bypasses this directly in _setObject which
   in turn calls manage_afterAdd both on the initial construction and when the
   policy is attached to the tool, make all the manage_afteradd methods in the
   product reentrant.

 - the new xml dictionary io, wasn't handling default paths that were designed to
   place deploy dirs into the examples/static directory, fixed. also make
   default paths locations perform platform specific separator handling.

 - make the plone 2.1 example policy utilize default path handling instead of
   hardcoding to /usr/local location.

 - allow specification of system user for rendering.

 - add a new example, which performs backups of file content in the portal.

------------------------------------------------------------------------
r1397 | hazmat | 2006-06-25 23:15:44 -0700 (Sun, 25 Jun 2006) | 1 line

make lack of default transports fail gracefully, which allows for better compatiblity with windows.