collective.cmfeditionsdexteritycompat 0.1b8

Makes `Products.CMFEditions`_ works with `Dexterity` content types.

Introduction

This package makes Products.CMFEditions works with Dexterity content types.

In general CMFEditions works ok with Dexterity. The only problem is the versions_history_form template: it does not show the older versions for Dexterity content items. Also, it may break if the custom content type does not use the default view auto-generated by Dexterity.

This package solve this problem by overriding versions_history_form.

Installation

The usual: add this package to the buildout and install the Generic Setup profile in the Plone Site.

Extension/customization points

To make the versions_history_form template work with Dexterity content types some views were created. These can be overriden to customize the way older versions of a content type are displayed:

• @@download-version: Downloads an older version of a file stored in a plone.namedfile field.

• @@content-core: Render only the content-core div of the default view of a content item.

• @@version-view: Same as @@content-core but makes links to file downloads use the @@download-version view.

Changelog

0.1b8 (2012-09-17)

• Fixed failing test on Plone 4.1.6

• Changed requirement from Plone to Products.CMFPlone

0.1b7 (2011-08-22)

• Synced template override with CMFEditions trunk.

0.1b6 (2011-08-19)

• Removed import of Products.CMFEditions.setuphandlers.DEFAULT_POLICIES make it compatibile with Products.CMFEditions >= 2.1.0

0.1b5 (2011-08-01)

• Do not extract the “content-core” div from the default view HTML code anymore in “@@content-core”. Now we provide a default “@@content-core” based on the default views provided by Dexterity.

0.1b4 (2011-08-01)

• Fixed bug: Unauthorized error when content type has custom view set up with Grok.

0.1b3 (2011-07-20)

• Fixed tests again.

0.1b2 (2011-07-13)

• Fixed tests.

0.1b1 (2011-07-12)

• Initial release