redturtle.monkey
Another MailChimp integration for Plone. We did have a reason to not use collective.mailchimp nor collective.chimpfeed (although we have reused/shared some of the concepts you can find there). Simply our use case is different (call it much simpler :)
Use case
Let say you want to configurate MailChimp campaign in Plone (including Plone content of course) and manually decide when to push it to chimp cloud service. This is what the redturtle.monkey actually do. You can:
create multiple campaign configurations
each configuration:
can contain different MailChimp API Keys (or you can use global ones)
contain different Plone items to be used as campaign content
can have a MailChimp template and subscribers list
Sections/Slots
What makes redturtle.monkey flexible is the ability to register custom MailChimp template sections (slots) and decide how to render them. A section is subscriber adapter that you can register with ZCML like that:
<subscriber provides="redturtle.monkey.interfaces.IMailchimpSlot"
factory=".generic.Body" />
Then the factory is simple:
from redturtle.monkey.slots import Slot class Body(Slot): name = u'body'
The name will be used later by MailChimp so it should correspondent to your mc:edit tag.
Last thing is to register content renderer for your new slot:
<adapter for="* *" factory=".generic.BodyRenderer" name="body"/>
but if you would like to render let say events differently you can do it:
<adapter for="Products.ATContentTypes.interfaces.IATEvent *"
factory=".event.BodyRenderer" name="body"/>
It will then look like that:
from Products.Five.browser.pagetemplatefile import ViewPageTemplateFile
from redturtle.monkey.slots import SlotRenderer
class BodyRenderer(SlotRenderer):
template = ViewPageTemplateFile("generic_body.pt")
Changelog
1.3.0 (2017-03-27)
Added possibility to move items in the table during the first step of the wizard [pnicolli]
1.2.1 (2014-08-04)
fixed translation issues [keul]
added script for compile translations [keul]
fixed issue that was showing empty site when surfing “Campaign’s items” settings [keul]
1.2 (2013-03-26)
subscribe portlet now supports multi campaigns [amleczko]
1.1 (2013-03-12)
translation fixes [amleczko]
portlet hidden for anonymous [amleczko]
make sure only published content is used [amleczko]
1.0 (2013-03-05)
Initial release
Metadata
Release files for redturtle.monkey 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| redturtle.monkey-1.3.0.tar.gz | 44.6 kB | Without provenance | Details for redturtle.monkey-1.3.0.tar.gz |
Release files / redturtle.monkey-1.3.0.tar.gz
| Download URL | redturtle.monkey-1.3.0.tar.gz |
|---|---|
| Size | 44.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
164b5e5c6d116e2b9ec122e67cf21d161c409a4b7191b15c44ef54d0dddb57a9
|
|
BLAKE2b-256 checksum How to use checksums |
070ee3a0901582eb49e2990624932428cbbe044936abeff5ffc6e30289771950
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for redturtle.monkey 1.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.