Introduction
This module adds a new rule type to Plone content rules system which is handled when a Plone event, or any content having a start date, will begin tomorrow, or within any delay.
First, add collective.contentrules.comingsoon package to the ‘eggs’ parameter of your buildout, or in the dependencies of your policy product, and restart your buildout.
Then you have to create a cron that calls once a day ‘@@comingsoon-notify’ view on site root, using a wget for example. (http://localhost:port/my/site/@@cominsoon-notify).
You may use z3c.recipe.usercrontab recipe that manages cron tasks from buildout: http://pypi.python.org/pypi/z3c.recipe.usercrontab/
Then, you can add ‘Coming soon’ rules to your content rules. Those rules will be handled on each event content whose start date is among a defined delay.
The notification delay can be set on ‘Coming soon’ configuration page. The default delay is one day.
Changelog
1.2 (2013-03-27)
It is now possible to use per content type delays ! [cedricmessiant]
1.1 (2012-12-21)
index is now a view parameter (for example, for expirationDate : @@comingsoon-notify?index=expires) [cedricmessiant]
Update buildout [cedricmessiant]
1.0.2 (2011-04-28)
Add buildout & bootstrap. [toutpt]
Add dependency of plone.app.registry in default profile and upgrade step. [toutpt]
1.0.1 (2011-04-27)
Avoid ComponentLookupError with Plone 4.0. [thomasdesvenain]
1.0 (2011-04-06)
Initial release. [thomasdesvenain]
6 maintainers
Metadata
6 maintainers
Release files for collective.contentrules.comingsoon 1.2
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.contentrules.comingsoon-1.2.zip | 33.4 kB | Without provenance | Details for collective.contentrules.comingsoon-1.2.zip |
Release files / collective.contentrules.comingsoon-1.2.zip
| Download URL | collective.contentrules.comingsoon-1.2.zip |
|---|---|
| Size | 33.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ddd4f76afe4ef97756b7da8acc8df3eee5b7b7d10b903cea6862bd466e248639
|
|
BLAKE2b-256 checksum How to use checksums |
9c7f4aac602a12d6b14883324c3523f2ac630ede590a417991ffdf616c7337ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.contentrules.comingsoon 1.2
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.
