Introduction
This add-on extends plone.app.registry by adding a contextual registry which can be used over any object. It has been created to store view configuration throw the add-on collective.configviews 2.X
How to use this add-on
As a developer you can get the IRegistry adapter from a content object and next use it as you want to get/set your configuration stuff.
As a content administrator you can manage the configuration stored in a content by calling the view $content_url/contextual_registry/view where $content_url must be replaced by the url of your content item.
How to install
Please follow the official documentation.
Credits
Changelog
1.0 (2012-01-30)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for collective.registry 1.0
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.registry-1.0.tar.gz | 16.0 kB | Without provenance | Details for collective.registry-1.0.tar.gz |
Release files / collective.registry-1.0.tar.gz
| Download URL | collective.registry-1.0.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
40a3a72b0b3897f4a24e263e8604592cf59f4287b1e196e908018e2886eb31e5
|
|
BLAKE2b-256 checksum How to use checksums |
f97918ff998081a78171f9688a9fbea847c8735899bd22296744dbbf5bab5167
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.registry 1.0
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.
