plone.contentrules 2.0.3

Plone ContentRules Engine

Overview

plone.contentrules provides a “pure Zope” implementation of a a rules engine which allows arbitrary conditions and actions to be combined into rules, and rules to be executed dependent on events.

You can think of this as somewhat similar to user-assembled mail filtering rules or something like Apple’s Automator. It is used by plone.app.contentrules to provide such functionality for Plone.

Changelog

2.0.3 (2013-06-13)

• Fix: Plone 4.3 sites were broken by “Content added” content rules created before 4.3. [thomasdesvenain]

2.0.2 (2013-01-13)

• Field descriptions on add form are consistent with the ones in edit form. [thomasdesvenain]

• Add MANIFEST.in. [WouterVH]

2.0.1 - 2011-04-01

• Event types vocabulary is internationalized. This closes http://dev.plone.org/plone/ticket/7059. This closes http://dev.plone.org/plone/ticket/6902. [thomasdesvenain]

2.0 - 2010-07-18

• Update license to GPL version 2 only. [hannosch]

2.0b1 - 2010-06-13

• Cleaned up package metadata. [hannosch]

• Use zope.container instead of its older zope.app variant. [hannosch]

• Cleaned up tests to rely on a minimal amount of packages. [hannosch]

• Clarified license and copyright. [hannosch]

• Specify package dependencies. [hannosch]

1.1.0 - 2008-04-20

• Unchanged from 1.1.0a1

1.1.0a1

• Merge PLIP 204 - GenericSetup support. A contentrules.xml file can now be used to import and export rule definitions and assignments. [optilude]

1.0.5

• Use the plone i18n domain for text found in metadirectives.py. [hannosch]

• Added i18n markup to the IRuleConfiguration schema, which is used in a user-visible configuration. This closes http://dev.plone.org/plone/ticket/6886. [hannosch]