This release is a pre-release and may not be stable for production use.
Introduction
With collective.multitemplate you can register more than one template for a portlet and when adding such a portlet you can select which template to use for rendering the portlet. It’s similar to the ‘display’ menu for content.
Usage
A portlet needs to support collective.multitemplate by using collective.multitemplate.portlet.Assignment as the base class for assignments and use collective.multitemplate.portlet.ViewMultiTemplate by wrapping the default template like this:
render = ViewMultiTemplate(ViewPageTemplateFile("portlet.pt"))
It is then possible to define additional templates with code snippets like:
additional_template = MultiTemplate(ViewPageTemplateFile("portlet2.pt"))
and zcml like:
<adapter factory=".portlet.additional_template" for=".portlet.Renderer" provides="collective.multitemplate.IMultiTemplate" name="Additional template" />
The registration of additional templates can live in a different package then the original portlet.
Changelog
1.0b1 - 2009-09-22
Initial release
Metadata
Release files for collective.multitemplate 1.0b1
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.multitemplate-1.0b1.zip | 13.5 kB | Without provenance | Details for collective.multitemplate-1.0b1.zip |
Release files / collective.multitemplate-1.0b1.zip
| Download URL | collective.multitemplate-1.0b1.zip |
|---|---|
| Size | 13.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
95bdae9c119a5a3549b4852f1a40a69f0e8343be0ba5801ef2efeea5fa2160b8
|
|
BLAKE2b-256 checksum How to use checksums |
209969ba592bf56af0577e29b0f0fe4f4d69b54717e9810f16bcafa1954f5fa1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.multitemplate 1.0b1
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.