You are not logged in Log in Join
You are here: Home » Members » ensane » CMFDynamicDocument » README » View Document

Log in
Name

Password

 

README

CMFDynamicDocument 1.1.2 beta README

The 1.1.2 beta release includes one major change. I've added 'document' to
the context namespace of the product. I originally thought I would expect
'here' to be the document, but this then changes the behavior of this as a
pagetemplate from the pagetemplate product. To alleviate this strangeness,
I felt it was best to simply add the document to the namespace.

In addition to this major contextual change, there were a couple minor templating
changes and clean up of the package. Removal of the .diff and .rej files and
explicitly changing the content type module to use it's own view template.

I also added Title and Description edit fields to the ddocument_edit_form
template and added settr handling to the ddocument_edit.py script. This is
more in line with how I'm used to editing content types - I seldom use the
Metadata forms for editing content types.

The 1.1.12 release includes a patch provided by the Plone community which
adds support for Plone (as well as maintains existing support for standard
CMF releases. If you encountrer problems with this, please let me know; as
they are untested by myself.
The CMFDynamicDocument product is a hybrid of the CMFDefault Document and
PageTemplates. It allows content authors to include TAL, TALES and METAL
in CMF document content objects.
See http://dev.zope.org/Wikis/DevSite/Projects/ZPT/LanguageSpecifications
for more details on the Language Specifications of ZPT.
The CMFDynamicDocument has been tested with at least TAL Specification 1.4,
TALES Specification 1.3, and METAL Specification 1.0 as well as the versions
included in the Zope-2_6-branch

A caveat from fully conforming to the PageTemplate is that we only support
presentation in the form of an HTML document. XML is not currently supported
in version 1.1.11.

See the INSTALL.txt file for how to get the product installed
within your CMF and any upgrade issues.

Use at your own risk. :-p