Introduction
Portlet extension for the Plone suite Monet Calendar.
It add a new portlet type (designed for beeing used where wide space is available, like inside a collective.portletpage area) that display results and view taken from a calendar section inside the site. You can also provide additional filters on the portlet itself.
Credits
Developed with the support of:
All of them supports the PloneGov initiative.
Changelog
0.4.1 (2014-10-27)
Fix problem with new plone calendar portlet: need data-year and data-month attributes [lucabel].
0.4.0 (2014-10-08)
Plone calendar portlet customization moved here from monet.calendar.extensions [keul]
0.3.0 (2011-12-06)
fixed portlet permission to a better ones (also compatible with Plone 4.1) [keul]
added the default values to the __init__ parameters into the assignment of portlet [mirco]
0.2.0 (2011-05-11)
fixed italian translation [keul]
fixed a bug that make the portlet broken when specifying 0 and 0 in “days” paramenter [keul]
added Header as link portlet option, for make the portlet title clickable [keul]
0.1.0 (2011-05-09)
Initial release
Metadata
Release files for monet.calendar.portlet 0.4.1
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 |
|---|---|---|---|---|
| monet.calendar.portlet-0.4.1.tar.gz | 19.0 kB | Without provenance | Details for monet.calendar.portlet-0.4.1.tar.gz |
Release files / monet.calendar.portlet-0.4.1.tar.gz
| Download URL | monet.calendar.portlet-0.4.1.tar.gz |
|---|---|
| Size | 19.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6cd405321eb258d4857220d09f8f194753a05a27c6ca7ac33a2e55d60040fd18
|
|
BLAKE2b-256 checksum How to use checksums |
7c8c0ca11c4574ce81f49c2f0a1de82d59deb772bf4eed642618f197b9800a65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for monet.calendar.portlet 0.4.1
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.