Introduction
This portlet was made to make it easier to relate or group objects using collections. An example would be to implement series of events. you relate manually each event with the same collection and then you can have a portlet that says for example: “More events from this series”
Changelog
0.3 (2013-03-12)
If all the events are past then do not hide them anymore.
0.2 (2013-02-27)
Do not show past events.
0.1dev (unreleased)
Initial release
2 maintainers
Metadata
2 maintainers
Release files for collective.portlet.manualRelated 0.3
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 | |
|---|---|---|---|---|
| collective.portlet.manualRelated-0.3.tar.gz | 15.1 kB | Without provenance | Details |
Release files / collective.portlet.manualRelated-0.3.tar.gz
| Download URL | collective.portlet.manualRelated-0.3.tar.gz |
|---|---|
| Size | 15.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6986c90adf6b3405c005249e028119fb8c0453378b162542fb939c6825c11c1d
|
|
BLAKE2b-256 checksum How to use checksums |
4e16eaea1c20d3a3352479d15d463f96e0e102052c203b9ed2b68c2662b8d3d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.portlet.manualRelated 0.3
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.
