plone.app.contenttypes offers default content types for Plone based on Dexterity. This package replaces Products.ATContenttypes and will provide the default-types in Plone 5.

Warning: plone.app.contenttypes can be used on a new site without problems. Using it on a site with existing content requires migrating the sites content and is only recommended if you know what you're doing! Please see the chapter "Migration"

It contains the same types as default Plone does:

• Folder
• Document
• News item
• File
• Image
• Link
• Event (Using behaviors from plone.app.event)
• Collection (this already replaces plone.app.collection which is no longer needed then)

The main difference from a users perspective is that these types are extendable through-the-web. This means you can add or remove fields and behaviors using the control-panel "Dexterity Content Types" (/@@dexterity-types).

The aim is to mimick the old default-types as closely as possible, not to change the content-creation experience for editors.

plone.app.contenttypes has been merged into the Plone 5.0 branch and will be shipped with the next Plone release: https://dev.plone.org/ticket/12344

plone.app.contenttypes works with Plone 4.1+

Add this line in the eggs section of your buildout.cfg:

eggs =
    ...
    plone.app.contenttypes

If you have a mixed Plone site with Archetypes content and dexterity content use the extra requirement:

``plone.app.contenttypes ['atrefs']``

If you install plone.app.contenttypes on a fresh site (i.e. when no content has been edited or added) the existing default-content will be replaced by dexterity-content to make sure it is still editable.

If you install plone.app.contenttypes in a existing site all Archetypes-based content of the default Types still exists and can be viewed but can't be edited. On installation plone.app.contenttypes removes the type-definitions for the old default-types like this:

<object name="Document" remove="True" />

To make this content editable egain you need to migrate it to Dexterity (please see the section on migration) or uninstall plone.app.contenttypes.

Archetypes-based content provided by add-ons like Products.PloneFormGen will still work since only the default-types are replaced.

To remove plone.app.contenttypes and return full functionality to old content and restore the AT-based default-types you have to install the import step "Types Tool" of the current base profile. Follow the following steps:

• in the ZMI navigate to portal_setup and the tab "import"
• in "Select Profile or Snapshot" leave "Current base profile (<Name of your Plonesite>)" selected. This is usually Products.CMFPlone
• select the Types Tool (usually Step 44)
• click "import selected steps"

Any content you created based on plone.app.contenttypes will not be editable until you reinstall plone.app.contenttypes.

Warning: Migrations are in an early stage and might break your site in some cases! Please read this thoroughly!

To migrate your content from Archetypes to Dexterity use the form at /@@atct_migrator.

plone.app.contenttypes includes migrations for the following use-cases:

• from default Archetypes-based types to plone.app.contenttypes
• from older versions of plone.app.contenttypes to current versions

Migrations that will be will come in future version:

• from old plone.app.contenttypes-event to DX-plone.app.event
• from AT-plone.app.event to DX-plone.app.event
• from atct ATEvent to DX-plone.app.event
• from ATTopic to DX-plone.app.collections
• from AT-plone.app.collection to DX-plone.app.collections

There is a working migration from atct ATEvent to AT-plone.app.event in the plone.app.event package implemented as an upgrade step.

For migrations to work you need at least Products.contentmigration = 2.1.3 (part of Plone since Plone 4.2.5) and plone.app.intid (part of Plone since Plone 4.1.0).

plone.app.contenttypes can migrate the following types:

• Folder
• Document
• News item
• File
• Image
• Link
• Collection

Since LinguaPlone does not support Dexterity you need to migrate from LinguaPlone to plone.app.multilingual (http://pypi.python.org/pypi/plone.app.multilingual). The migration from Products.LinguaPlone to plone.app.multilingual should happen before the migration from Archetypes to plone.app.contenttypes. For details on the migration see http://pypi.python.org/pypi/plone.app.multilingual#linguaplone-migration

Before version 1.0a2 the content-items did not implement marker-interfaces. They will break in newer versions since the views are now registered for these interfaces (e.g. plone.app.contenttypes.interfaces.IDocument). To fix this you can call the view /@@fix_base_classes on your site-root.

The migration should warn you if any of your types are extended with archetypes.schemaextender. The data contained in these fields will be lost.

You need to implement a custom migration for your types and dexterity-behaviors for the functionality provided by the schemaextenders. This is an advanced development task and beyond the scope of this documentation.

Custom content will not be changed by plone.app.contenttypes and should continue to work as expeced. However if you'd like to migrate your content-types to Dexterity (you'll have to create these types in Dexterity first) you might want to have a look at the code of plone.app.contenttypes.migration.migration.NewsItemMigrator as a blueprint.

• plone.app.dexterity. Dexterity is shipped with Plone 4.3.x. Version pins for Dexterity are included in Plone 4.2.x. For Plone 4.1.x you need to pin the correct version for Dexterity in your buildout. See Installing Dexterity on older versions of Plone <http://developer.plone.org/reference_manuals/external/plone.app.dexterity/install.html#installing-dexterity-on-older-versions-of-plone>.
• plone.app.collection.

When you try to install plone.app.contenttypes in a existing site you might get the following error:

(...)
Module Products.GenericSetup.utils, line 509, in _importBody
Module Products.CMFCore.exportimport.typeinfo, line 60, in _importNode
Module Products.GenericSetup.utils, line 730, in _initProperties

ValueError: undefined property 'schema'

Before installing plone.app.contenttypes you have to reinstall plone.app.collection to update collections to the version that uses Dexterity.

The schemata of the types are set in xml-files using plone.supermodel. This allows the types to be editable trough the web.

If you want to extend these types with code consider using behaviors.

• The image of the News Item is not a field on the contenttype but a behavior that can add a image to any contenttypes (similar to http://pypi.python.org/pypi/collective.contentleadimage)
• The functionality to transform (rotate and flip) images has been removed.
• There is no more field Location. If you need georeferenceable consider using collective.geo.behaviour
• The link on the image of the newsitem triggers an overlay
• the link-type has the additional functionality to use the variable ${navigation_root_url} and ${portal_url}.

GNU General Public License, version 2

• Philip Bauer <bauer@starzel.de>
• Michael Mulich <michael.mulich@gmail.com>
• Timo Stollenwerk <contact@timostollenwerk.net>
• Peter Holzer <hpeter@agitator.com>
• Patrick Gerken <gerken@starzel.de>
• Steffen Lindner
• Daniel Widerin
• Jens Klein <jens@bluedynamics.com>
• Joscha Krutzki <joka@jokasis.de>
• Mathias Leimgruber <m.leimgruber@4teamwork.ch>
• Matthias Broquet <mbroquet@atreal.fr>