Introduction
This package provides an alternative full view for Plone with support for BrowserViews. BrowserViews weren’t fully supported in the skin layer based folder_full_view Page Template. This package provides a @@full_view view.
This package fixes: “Error when view folder with folder_full_view view” http://code.google.com/p/dexterity/issues/detail?id=172
Changes
1.3 (2013-11-23)
Register “en” and “de” translations. [thet]
1.2 (2013-02-06)
Allow recursive expansion of full_view views. [thet]
1.1.1 (2013-01-18)
Fix pfg_prefix for PloneFormGen forms to really return a unique prefix per form in a full_view. [thet]
1.1 (2013-01-16)
Render PloneFormGen FormFolder not via the content-core macro but via an @@embedded view. [thet]
1.0 (unreleased)
Initial release.
2 maintainers
Metadata
2 maintainers
Release files for collective.fullview 1.3
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 | |
|---|---|---|---|---|
| collective.fullview-1.3.tar.gz | 12.9 kB | Without provenance | Details |
Release files / collective.fullview-1.3.tar.gz
| Download URL | collective.fullview-1.3.tar.gz |
|---|---|
| Size | 12.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71dbe31d2a8a8872d40f0fdb294f8b153d5144658ed4a20fa314a2606f529b16
|
|
BLAKE2b-256 checksum How to use checksums |
5ae2b742d550b38968f42ae0acc76448a20b473191db63cf4e7976a7ae486a65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.fullview 1.3
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.
