Introduction
Cron
You have to create a daily cron to check digests to produce
0 4 * * * wget –http-user=zopescheduler –http-password=TrigOtad3 http://localhost:8080/mysite/@@digest-cron?maildigest-debug-mode=1 -O /dev/null
Manually check
http://localhost:9880/mysite/@@digest-cron -O /dev/null
Tests
This add-on is tested using Travis CI. The current status of the add-on is :
Changelog
1.0 (2014-10-10)
Feature: We can select recursive subscription: user can choose to be notified to the activity in the subfolders of the subscription folder. [thomasdesvenain]
Feature: Added ‘move’ activity notified when we cut/paste content and ‘publish’ activity when we publish content. Copied contents notifies add activity. [thomasdesvenain]
UI: Added ui for monthly email. More generic management of delays. [thomasdesvenain]
Plone 4.2+ and recent jQuery compatibility. [thomasdesvenain]
API: Rewrite collective.maildigest api so we don’t deal with collective.subscribe api outside of main utility. Use plone.api. [thomasdesvenain]
Fix: Do not break site when it is not installed. Do not need to install collective.inviting. [thomasdesvenain]
Fix: move activity is not handled when we delete a content. [thomasdesvenain]
Quality: New bootstrap and buildout. [thomasdesvenain]
Quality: Added tests and coverage. [thomasdesvenain]
IMPORTANT: because of changes in storage, before updating to this release, first run www.mysite.com/@@digest-cron?maildigest-debug-mode=1, otherwise you will loose some notifications.
0.3.3 (2014-01-28)
The previous copy/paste fix wasn’t enough, now fix copy/paste folder. [vincentfretin]
0.3.2 (2012-12-16)
Avoid error on copy/paste action. [thomasdesvenain]
Avoid Invalid error for anonymous on viewlet.
0.3.1 (2012-08-24)
More robust: ignore not IUUIDAware contents, manage subscriptions on site root. [thomasdesvenain]
0.1 (2012-08-03)
Package created using templer [thomasdesvenain]
3 maintainers
Metadata
3 maintainers
Release files for collective.maildigest 1.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 |
|---|---|---|---|---|
| collective.maildigest-1.0.zip | 62.5 kB | Without provenance | Details for collective.maildigest-1.0.zip |
Release files / collective.maildigest-1.0.zip
| Download URL | collective.maildigest-1.0.zip |
|---|---|
| Size | 62.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3bfa5e16115677bc812382ccee76b6f19c37732c5805f6af299170cf39f79efe
|
|
BLAKE2b-256 checksum How to use checksums |
28dc85dd54acc09cbfddeca441b2918ff338b40f0dcdc12e7424dadfe8c21e5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.maildigest 1.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.
