This release is a pre-release and may not be stable for production use.
Introduction
The ContentLicensing tool allows for both a site wide copyright license to be set by default, and the ablility to set licenses on individual objects. It supports a number of licenses including all rights reserved, GFDL, and Creative Commons (with an integrated license picker). You can also enter and select licenses not supported by default, or configure new licenses that will appear in the selection widget for your Plone instance.[
Changelog
2.2.0 - Final
express additional metadata fields in rss views
fix invalid CSS issues
2.1.0 - Unreleased
Initial release
Release files for collective.contentlicensing 2.2.0-final
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.contentlicensing-2.2.0-final.tar.gz | 80.7 kB | Without provenance | Details for collective.contentlicensing-2.2.0-final.tar.gz |
Release files / collective.contentlicensing-2.2.0-final.tar.gz
| Download URL | collective.contentlicensing-2.2.0-final.tar.gz |
|---|---|
| Size | 80.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
248661ce9b728484238e6f75bc30606687cae73b142193cb8fed176dffea8600
|
|
BLAKE2b-256 checksum How to use checksums |
8cda579a72ff8d88182a5d7f494055b2d2bb7903a50b97f9711586e9de3e01c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.contentlicensing 2.2.0-final
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.
