This release is a pre-release and may not be stable for production use.
Introduction
This is a sitemap replacement that:
shows only a branch of the tree, if called in a context different than the site root
takes a sitemapDepth request parameter, overriding the global one in navtree_properties
Both features are available to users with the collective.deepsitemap: Use Deep Sitemap permission (by default for Manager).
Note
This product keep the normal Plone behavior with the “sitemap” link. The additional parameter is designed for “one-time” request, for special needs of the site administrator.
Credits
Developed with the support of Azienda USL Ferrara; Azienda USL Ferrara supports the PloneGov initiative.
Changelog
1.0a (2011-06-14)
initial release
Metadata
Release files for collective.deepsitemap 1.0a
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.deepsitemap-1.0a.tar.gz | 11.8 kB | Without provenance | Details for collective.deepsitemap-1.0a.tar.gz |
Release files / collective.deepsitemap-1.0a.tar.gz
| Download URL | collective.deepsitemap-1.0a.tar.gz |
|---|---|
| Size | 11.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21403cc1b9dc6bf68f102f73cb8201ea3e2fd95d73726f80e27d868f9fc340db
|
|
BLAKE2b-256 checksum How to use checksums |
4c11af0ffd0719b90659abc5d74da1bba24d8832dd462501d32edaf71d6d2423
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.deepsitemap 1.0a
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.