This release is a pre-release and may not be stable for production use.
Overview
This package makes it easy to designate content into one or more named feeds, suitable for creating automated newsletter content.
It extends the base content schema for any Archetypes-based content which lets editors easily manage which feeds (if any) that a given item should be listed under.
Designed for the MailChimp internet service, the package also includes a subscription portlet that optionally lists a subset of interest groups.
Compatibility
Tested on Plone 4.0.
Getting started
First, install the product using Plone’s add-on control panel.
Visit the “MailChimp RSS” control panel to define one or more feeds.
Enable one or more feeds for your content by clicking “Edit” and selecting from the “Feeds” option.
Optionally,
Configure a MailChimp API-key (also available in the control panel).
Add one or more subscription portlets.
Localization
The product is currently localized into:
Danish
Contributions are welcome!
Changes
1.0-beta1 (2012-01-16)
Initial public release.
Release files for collective.chimpfeed 1.0-beta1
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 |
|---|---|---|---|---|
| collective.chimpfeed-1.0-beta1.tar.gz | 30.3 kB | Without provenance | Details for collective.chimpfeed-1.0-beta1.tar.gz |
Release files / collective.chimpfeed-1.0-beta1.tar.gz
| Download URL | collective.chimpfeed-1.0-beta1.tar.gz |
|---|---|
| Size | 30.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5e50a28d8c76dbe599b6f382a1357165594833925a501465d8bcc162c225defe
|
|
BLAKE2b-256 checksum How to use checksums |
0a0afde73304b7964f04fede0c8cfbfdee8d1d56b0060e4dba7fd7404e15ed55
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.chimpfeed 1.0-beta1
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.
