Skip to main content

Flexible mail content rule

Project description

Introduction

This package provides an extended content rule “mail” action with many more variable substitutions available, including the name and email address of the content owner, making it possible to email the owner of a piece of content.

It is also possible to provide new “replacers” by writing an interface with an associated adapter and registering a new IMailModel utility. The user is able to pick the replacer to use on the action edit form.

Changelog

0.3 - 2009/03/24

  • Added a note in the UI about how to use variables. [optilude]

  • The ‘source’ field is not required, but would throw an error if not filled in. This is now fixed. [optilude]

0.2 - 2009/03/24

  • Made the executor fail gracefully if the content being acted upon is not adaptable to the replacer interface. [optilude]

  • Made the default replacer adapt any Dublin Core-capable content, avoiding an unnecessary dependency on Archetypes. [optilude]

  • Made the default IMailModel implementation more re-usable. [optildue]

  • Updated documentation and interface specifications. [optilude]

  • Fixes actions/configure.zcml in order to play nice with GenericSetup

0.1 - Unreleased

  • Initial release

Project details


Download files

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

Source Distribution

collective.contentrules.mail-0.3.tar.gz (14.8 kB view details)

Uploaded Source

File details

Details for the file collective.contentrules.mail-0.3.tar.gz.

File metadata

File hashes

Hashes for collective.contentrules.mail-0.3.tar.gz
Algorithm Hash digest
SHA256 bbbb5ee35fd5bb061ff8c7cdba6fcf6992c617999b958d8f0d6178a168db6a40
MD5 160fa9305d6978bfb77f67c181922a25
BLAKE2b-256 e8bf9138fd9156f51dc380bb9c169eeb11b590f94aad540a7da964f5491fe21e

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page