21. Dexterity II: Talks

In this part you will solve the following task:

  • Create a contenttype ‘talk’ to store all the data required for a talk

Topics covered:

  • Registration and configuration of content types

  • Schema

  • Fields

  • Widgets

21.1. The type registration

Create a new file types.xml add them it your add-on package in profiles/default/


That is backend/src/ploneconf.site/src/ploneconf/site/profiles/default/types.xml

This will tell Plone that there is a new content type defined in file talk.xml.

<?xml version="1.0"?>
<object name="portal_types" meta_type="Plone Types Tool">
  <object name="talk" meta_type="Dexterity FTI"/>

Plone will now expect a file profiles/default/types/talk.xml and will register that as a new content type.

21.2. The fti

Add the file ploneconf/site/profiles/default/types/talk.xml. Note that there is a file types and a folder types.

This is the Factory Type Information that holds the configuration for the content type talk.

<?xml version="1.0"?>
<object name="talk" meta_type="Dexterity FTI" i18n:domain="plone"
 <property name="title" i18n:translate="">Talk</property>
 <property name="description" i18n:translate=""></property>
 <property name="icon_expr">string:${portal_url}/document_icon.png</property>
 <property name="factory">talk</property>
 <property name="add_view_expr">string:${folder_url}/++add++talk</property>
 <property name="link_target"></property>
 <property name="immediate_view">view</property>
 <property name="global_allow">True</property>
 <property name="filter_content_types">True</property>
 <property name="allowed_content_types"/>
 <property name="allow_discussion">False</property>
 <property name="default_view">view</property>
 <property name="view_methods">
  <element value="view"/>
 <property name="default_view_fallback">False</property>
 <property name="add_permission">cmf.AddPortalContent</property>
 <property name="klass">ploneconf.site.content.talk.Talk</property>
 <property name="schema">ploneconf.site.content.talk.ITalk</property>
 <property name="behaviors">
  <element value="plone.dublincore"/>
  <element value="plone.namefromtitle"/>
  <element value="plone.versioning" />
 <property name="model_source"></property>
 <property name="model_file"></property>
 <property name="schema_policy">dexterity</property>
 <alias from="(Default)" to="(dynamic view)"/>
 <alias from="edit" to="@@edit"/>
 <alias from="sharing" to="@@sharing"/>
 <alias from="view" to="(selected layout)"/>
 <action title="View" action_id="view" category="object" condition_expr=""
    description="" icon_expr="" link_target="" url_expr="string:${object_url}"
  <permission value="View"/>
 <action title="Edit" action_id="edit" category="object" condition_expr=""
    description="" icon_expr="" link_target=""
    url_expr="string:${object_url}/edit" visible="True">
  <permission value="Modify portal content"/>

Now our package has new configuration for Generic Setup. Generic Setup loads a lot of different types of configuration for the site from the folder profiles/. This configuration is applied to your site upon installing the package. This also means that you will need to reinstall the package once we are finished with the talk.

But the type is not yet complete since the schema (ploneconf.site.content.talk.ITalk) a the class (ploneconf.site.content.talk.Talk) that are referenced in the FTI are not yet there.

21.3. The schema

The schema holds the definition the fields that the content type will offer to store data.

In the fti we referenced the python-path ploneconf.site.content.talk.ITalk.

The module content does not exist. Create a folder content and add a empty __init__.py in it.


From the training root that is backend/src/ploneconf.site/src/ploneconf/site/content/__init__.py

You just created a python module :)

In this new folder add a file talk.py with the following content:

# -*- coding: utf-8 -*-
from plone.app.textfield import RichText
from plone.autoform import directives
from plone.dexterity.content import Container
from plone.namedfile.field import NamedBlobImage
from plone.schema.email import Email
from plone.supermodel import model
from ploneconf.site import _
from z3c.form.browser.checkbox import CheckBoxFieldWidget
from z3c.form.browser.radio import RadioFieldWidget
from zope import schema
from zope.interface import implementer
from zope.schema.vocabulary import SimpleTerm
from zope.schema.vocabulary import SimpleVocabulary

class ITalk(model.Schema):
    """Dexterity-Schema for Talks"""

    type_of_talk = schema.Choice(
        title=_(u'Type of talk'),
        values=['Talk', 'Training', 'Keynote'],

    details = RichText(
        description=_(u'Description of the talk (max. 2000 characters)'),

    audience = schema.Set(
            values=['Beginner', 'Advanced', 'Professional'],

    speaker = schema.TextLine(
        description=_(u'Name (or names) of the speaker'),

    company = schema.TextLine(

    email = Email(
        description=_(u'Email adress of the speaker'),

    website = schema.TextLine(

    twitter = schema.TextLine(
        title=_(u'Twitter name'),

    github = schema.TextLine(
        title=_(u'Github username'),

    image = NamedBlobImage(
        description=_(u'Portrait of the speaker'),

    speaker_biography = RichText(
        title=_(u'Speaker Biography (max. 1000 characters)'),

class Talk(Container):
    """Talk instance class"""

The first class ITalk is the schema for talks and defines quite a lot of different fields for different kinds of data.

  • The fields in the schema are mostly from zope.schema.

  • The most basic field is schema.TextLine which can store text.

  • In the next chapter you will find a reference of all field-types available in Plone.

  • In directives.widget(level=RadioFieldWidget) we change the default widget for a Choice field from a dropdown to radio-boxes.


21.4. The instance class

The second class Talk in talk.py will be the class of instances for each talk. It inherits from Container which is one of the default classes of dexterity. That is used for items that can contain other items. It does nothing so far but it can be useful later when we want to add methods or properties to it that can be used directly from a talk instance.

21.5. Try the new type

Now all pieces should be in place and you can enable the new type Talk.

  • Restart Plone (to load the new Python code and the changed zcml)

  • You do not need to restart the Volto frontend since we did not do any changes there.

  • Re-install the package ploneconf.site (deactivate and activate) to load the type registration and type configuration.

Now the new types should be visible in the add-menu.

You can test the type in the frontend (http://localhost:3000/add?type=talk) and in the backend (http://localhost:8080/Plone/++add++talk).


By default the frontend dies not render all fields, only the title and descriptions is visible. The server-side-rendered template instead iterates over all fields in your schema and displays them in a default way.

In one of the next chapters you will create a custom view for the new type.


Adding a talk in the frontend


Adding a talk in the backend

  • Test the type by adding a talk. Add some values in the fields, save it, look at the view and edit it again.

  • Compare all the fields you see to the code in the schema.

  • You can also make changes in the schema. After restarting the backend these changes are effective immediatley

  • Find the tool portal_types in the ZMI

  • Look at the fti for talk and inspect the configuration taken from the fti.

  • You can make changes to the fti here. Some of the configuration are also available in plone control panels where it makes sense. For example the dexterity-controlpanel http://localhost:3000/controlpanel/dexterity-types can modify the behaviors (defined in <property name="behaviors">) and http://localhost:8080/@@content-controlpanel has a checkbox for the setting <property name="global_allow">.

21.6. Summary

  • You created a custom content type.

  • You can now control the data that will be stored for talks.

  • You can reuse and adapt these examples to model data for your own use-cases.

  • Next up: After looking at even more fields that are available in Plone you will learn to change how talks are displayed.