Introduction
collective.contentstats adds a section to the Plone control panel showing summary statics of the content of the site. Specifically, it provides a table listing the number of content items broken down by portal type versus review state. Non-zero entries are linked to a listing of the respective items. Access to the page requires the ‘Manage portal’ permission.
Features
Works on catalog data exclusively - no content is touched.
Only lists portal types that are used
Only lists review states used
Works with custom add-ons right away
Supports CSV export of summary data
Tested with Plone 3.3.5 and 4.0.5
Changelog
1.0.1 (2011-05-09)
Get rid of setup.cfg
1.0 (2011-05-09)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for collective.contentstats 1.0.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 |
|---|---|---|---|---|
| collective.contentstats-1.0.1.tar.gz | 11.0 kB | Without provenance | Details for collective.contentstats-1.0.1.tar.gz |
Release files / collective.contentstats-1.0.1.tar.gz
| Download URL | collective.contentstats-1.0.1.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
52eaed96fe3efddc44e11de8dc2442e1c3e8112c2242fc34cce1658fe1f487c0
|
|
BLAKE2b-256 checksum How to use checksums |
1a02d6c209168414148684acf80a9963a7dba64e02e30c025eb0b0028fee7594
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.contentstats 1.0.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.
