What is the CMF?

The Zope Content Management Framework provides a set of services and content objects useful for building highly dynamic, content-oriented portal sites. The CMF provides the foundation for popular software packages such as Plone. It is intended to be easily customizable, in terms of both the types of content used and the policies and services it provides.

Where do I get it?

For release files, change logs, installation instructions and more please visit http://www.zope.org/Products/CMF/CMF-2.1.0-beta.

Roadmap and release information can be found at http://www.zope.org/Products/CMF/docs/roadmap.

The CMF mailing list can be reached at the [email protected] address, to sign up please visit http://mail.zope.org/mailman/listinfo/zope-cmf.

Please file bug reports, feature requests or suggestions in the CMF bug collector at http://www.zope.org/Collectors/CMF.

What has changed since the last release?

IMPORTANT NOTE:

If you upgrade an existing CMF instance to CMF 2.1, please see INSTALL.txt for instructions on how to run a separate upgrade script.

New Features

• CMFCalendar: Zope3 style browser views are now used by default. An additional setup profile allows you to hook up the oldstyle skins and to make customizations TTW.
• DirectoryView: Added registerDirectory ZCML directive. Using the old registerDirectory method in __init__.py is now deprecated. See zcml.IRegisterDirectoryDirective for details.
• DirectoryView: Added support for non-product packages. This introduces new registry keys. Old registry keys stored in persistent DirectoryView objects are updated on the fly. (http://www.zope.org/Collectors/CMF/467)
• Document: Added two new methods for safety belt handling.
• setup handlers: Improved properties handler. It now works with properties using a default_charset other than UTF-8.
• Merged patches from Martin Aspeli to enable generating events before and after DCWorkflow transitions, and in the notify methods of the workflow tool (http://www.zope.org/Collectors/CMF/461).

Bug Fixes

• CMFUid.UniqueIdHandlerTool: Touching the internal UID value on a content item will not cause reindexing all indices anymore, only the specific UID index will be touched. (http://www.zope.org/Collectors/CMF/469)
• CMFCore.MembershipTool: Fixed inconsistent behavior where member lookup would take all user folders up to the Zope root into account whereas member area creation would not.
• CMFCore.MembershipTool/CMFDefault.MembershipTool: when using an object without a __nonzero__ but with a __len__ (ala CMFBTreeFolder) as a member folder, the createMemberArea method would believe there was no members folder if the folder was empty, and so would fail (change "not membersfolder" to "membersfolder is not None") .
• CMFDefault.File and CMFDefault.Image: Restored ZMI Cache tab which was lost in CMF 1.6.
• CMFCore.DynamicType: Fixed behaviour regarding default view. DynamicType was making it impossible to use a Zope3-style default view for CMF content types. (http://www.zope.org/Collectors/CMF/459)

Others

• Tool lookup and registration is now done "the Zope 3 way" as utilities. Please see docs/ToolsAreUtilities.txt for some developer notes.
• CMFCore utils: Marked minimalpath and expandpath as deprecated.
• The CMF now depends on Zope 2.10.2 or higher.