Skip to main content

Default content types for Plone based on Dexterity

Project description

Introduction offers default content types for Plone based on Dexterity. This package is a replacement for the types in Products.ATContenttypes.

Warning: is best used when creating a new site from scratch. Using it on a site with existing content is not recommended if you don’t know exactly what you’re doing!

It contains the same types as default Plone does:

  • Folder
  • Document
  • News item
  • File
  • Image
  • Link
  • Event (this will be replaced by soon)
  • Collection (this is provided by

The main difference from a users perspective is that these types are extendable through-the-web. This means you can go to the control-panel (.../@@dexterity-types) and add or remove fields and behaviors for the existing types.

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

There is a PLIP to include in Plone 4.4:

Compatability works with Plone 4.1+


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

eggs =

Installing in an existing Plone-site

When you try to install 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 you have to reinstall to update collections to the version that uses Dexterity.

What happens to old content?

The old Archetypes-based content still exists and can be viewed but can’t be edited. On installation removes the type-definitions for the old default-types like this:

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

You can also migrate the old items to the types provided by (see the section about migrations).


To remove, 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”


Warning: Migrations are still in an very early stage and might break your site! is best used when creating a new site from scratch. Please proceed at your own risk!

For migrations to work you need at least Products.contentmigration = 2.1.3 which was not released at the time of writing.

This version comes with migrations for the following use-cases:

  • from default Archetypes-based types to
  • from older versions of to current versions

Migrations that will be will come in the future:

  • from old p.a.c.-event to
  • from default ATEvent to
  • from ATTopic to
  • from to

Migrating Archetypes-based content to can migrate the following types:

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

To migrate existing content go to /@@migrate_from_atct.


  • disable linkintegrity
  • LP
  • Plone-Version older tan 4.1.x need

Migrating content that is translated with LinguaPlone

Warning: This use-case has not yet been thoroughly tested!*

Since LinguaPlone does not support Dexterity you need to migrate from LinguaPlone to ( The migration from Products.LinguaPlone to should happen before the migration from Archetypes to For details on the migration see

Migrating from old versions of

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.`). To fix this you can call the view ``/@@fix_base_classes on your site-root.

Migrating content that was extended with archetypes.schemaextender

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

How to create a new page with only Dexterity

You have two options:

1. By hand

Installing remove the types automatically, you only have to remove the existing content (front-page, events, news, members).

2. Automatically

If you start from scratch you can want to try using a special branch of Products.CMFPlone that gives you the choice between Dexterity and Archetypes when creating a new site. This way you get a brand new site with

Modify your buildout to automatically pull the branch using mr.developer (

extensions = mr.developer
auto-checkout =

Products.CMFPlone = git
Products.ATContentTypes = git branch=davisagli-optional-archetypes

Differences to Products.ATContentTypes

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


  • Dexterity is shipped with Plone 4.3.x. Version pinns for Dexterity are included in Plone 4.2.x. For Plone 4.1.x you need to pinn the correct version for Dexterity in your buildout. See “Installing Dexterity on older versions of Plone” on

Information for Addon-Developers

Differences to ATContentTypes Interfaces

How to:

  • extend the types ttw or with xml ()
  • export a extended CT into a package to overwrite the default
  • extend with behaviors
  • make types transateable
  • Addon-Products that are known to work with p.a.c


GNU General Public License, version 2


TODO: add all contributors

Thanks to

  • The organizers of the Plone-Conference 2011 in San Francisco for a great conference!
  • The organizers of the Wine-and-Beer-Sprint in Munich and Capetown in January 2013
  • The creators of Dexterity


1.0b2 (2013-05-31)

  • Fix translations to the plone domain, and some translations match existing translations in the plone domain. (ported from [bosim]
  • Fix atct_album_view and don’t use [pbauer]
  • Add constrains for content create with the Content profile [ericof]
  • Add SearchableText indexer to Folder content type [ericof]
  • Fix atct_album_view [pbauer]
  • Removed dependency for collective.dexteritydiff since its features were merged into Products.CMFDiffTool [pbauer]
  • Add test for behavior table_of_contents [pbauer]
  • Add migration for blobnewsitems as proposed in [pbauer]
  • Require cmf.ManagePortal for migration [pbauer]
  • Always migrate files and images to blob (fixes #26) [pbauer]
  • Add table of contents-behavior for documents [pbauer]
  • Add versioning-behavior and it’s dependencies [pbauer]
  • Remove image_view_fullscreen from the display-dropdown [pbauer]
  • Enable selecting addable types on folders by default [pbauer]
  • Fix reference-migrations if some objects were not migrated [pbauer]
  • Keep the order references when migrating [pabo3000]
  • Move templates into their own folder [pbauer]
  • Moved migration related code to specific module [gborelli]
  • Added migration Collection from app.collection to app.contenttypes [kroman0]
  • Add missing i18n:attributes to ‘Edit’ and ‘View’ actions of File type. [saily]
  • Bind ‘View’ action to ${object_url}/view instead of ${object_url} as in ATCT for File and Image type. [saily]
  • Fixed installation of p.a.relationfield together with p.a.contenttypes. [kroman0]
  • Fixed creating aggregator of events on creating Plone site. [kroman0]
  • Added titles for menuitems. [kroman0]
  • Hide uninstall profile from @@plone-addsite. [kroman0]
  • Fix ‘ImportError: cannot import name Counter’ for Python 2.6. [timo]
  • Move XML schema definitions to schema folder. [timo]
  • Prevent the importContent step from being run over and over again. [pysailor]
  • Add build status image. [saily]
  • Merge (Tag: 2.0b5) into [timo]
  • Refactor p.a.collection robot framework tests [timo]

1.0b1 (2013-01-27)

  • Added mime type icon for file. [loechel]
  • Lead image behavior added. [timo]
  • Make NewsItem use the lead image behavior. [timo]
  • SearchableText indexes added. [reinhardt]
  • Set the text of front-page when creating a new Plone [pbauer]
  • Robot framework test added. [Gomez]

1.0a2 (unreleased)

  • Move all templates from skins to browser views. [timo]
  • User custom base classes for all content types. [timo]
  • Migration view (@@fix_base_classes) added to migrate content objects that were created with version 1.0a1. [timo]
  • Mime Type Icon added for File View [loechel]

1.0a1 (unreleased)

  • Initial release

Project details

Release history Release notifications

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date (322.7 kB) Copy SHA256 hash SHA256 Source None

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page