skip to navigation
skip to content

collective.richdescription 1.0.1

Richtext/HTML Description field for Archetypes

Latest Version: 2.0


Adds the new html-formatable textfield “richdescription” to Archetypes based content types and hides the description field from ExtensibleMetadata. When the field is saved, the contents are also stored in the “description” field, but without html-formating. A Metadata index is provided, so that “richdescription” can be used with catalog brains. There is no folder_listing template yet, but if you want to have HTML formated descriptions in folder_listing, then use something like this:

  tal:define="item_description item/richdescription|nothing;
              item_description python:item_description or item.Description;">
  <p class="akaDescription"
    tal:content="structure item_description">DESCRIPTION</p>


Although there are no big issues with this package, use it at your own risk! The description field wasn’t meant to hold HTML data. People may tend to write long essays in the description field, which is not what you want, probably. Some use cases require this functionality though, so have fun.


There should be no need for a specific migration step. When no richdescription field is available for a content type, it falls back to the normal description field. When saving a content type, the richdescription field is set and the catalog’s metadata richdescription column is filled.


Tested with Plone 4


Johannes Raggam <>


1.0.1 (2014-06-13)

  • Metadata update. [thet]

1.0 (2012-11-07)

  • Initial release [thet]


  • When no description is set, return a BaseUnit as fallback. Fixes AttributeError, where original_encoding was tried to accessed on a string value. [thet]
  • Register the skins folder for any theme. [thet]
  • Initial version on 2010-10-05 for
File Type Py Version Uploaded on Size
collective.richdescription-1.0.1.tar.gz (md5) Source 2014-06-12 13KB