collective.tiles.collection
A tile that shows collection results with customizable layouts
Features
Emulates the old portlet collection behaviors
Mosaic-ready
Additional css class field, to append a custom css class to the tile container
Customizable layouts list
Installation
Install collective.tiles.collection by adding it to your buildout:
[buildout]
...
eggs =
collective.tiles.collection
and then running bin/buildout
Usage
You can’t use this tile without a tile manager (or maybe, you can if you create new tiles manually in some specific context) like Mosaic or redturtle.tiles.management
When you try to create a new collection tile, you have a form like the portlet’s one.
Customizable layouts
When you create/edit a collection tile, there is a field that allows you to select the final layout from a list. This list is generated with a specific set of view that satisfy following rules:
The Class must implement ICollectiveTilesCollectionLayer interface
In the Class there should be an attribute display_name with a human-readable title
The template need to define a macro called collection-tile-macro
This is an example:
configure.zcml:
<browser:page
name="additional_renderer"
permission="zope2.View"
for="*"
class=".additional_render.View"
layer=".interfaces.ISomeBrowserLayer"
template="additional_render.pt"
/>
additional_render.py:
from Products.Five.browser import BrowserView
from collective.tiles.collection.interfaces import ICollectionTileRenderer
from zope.interface import implements
from collective.tiles.collection import _
class AdditionalView(BrowserView):
implements(ICollectionTileRenderer)
display_name = _("Another tile layout")
additional_render.pt:
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"
xmlns:tal="http://xml.zope.org/namespaces/tal"
xmlns:metal="http://xml.zope.org/namespaces/metal"
xmlns:i18n="http://xml.zope.org/namespaces/i18n"
lang="en"
metal:use-macro="here/main_template/macros/master"
i18n:domain="collective.tiles.collection">
<body>
<metal:macro define-macro="collection-tile-macro">
...
</metal:macro>
</body>
</html>
Translations
This product has been translated into
Italian
Contribute
Credits
Developed with the support of:
Regione Emilia-Romagna supports the PloneGov initiative.
License
The project is licensed under the GPLv2.
Contributors
RedTurtle Technology, sviluppoplone@redturtle.it
Changelog
2.1.1 (2024-03-06)
Avoid error when getting collection by UID. [daniele]
2.1.0 (2023-11-28)
Add ‘Show Description’ option, default disabled to match rendering in previous versions of the tile. [fredvd]
Plone 6 support: Refactor Mosaic addon support to use zcml condition instead of using the quickinstaller tool. [fredvd]
Plone 6 support: Remove unused dependency on plone.formwidget.contenttree [fredvd]
2.0.0 (2022-09-14)
Drop includeDependencies=”.” in order to work with pip [mamico]
1.3.1 (2021-09-27)
Simplified and improved checks for registered renderers. [cekk]
1.3.0 (2021-09-10)
Python3 compatibility. [cekk]
Do not use templates registered from unavailable layers. [cekk]
1.2.1 (2021-05-07)
Fix translations. [cekk]
1.2.0 (2019-01-09)
Fixed permission to see empty tile collection message.
Fixed vocabulary source for schema choice in tile collecton to support pam. [eikichi18]
List of renderers is now sorted by title. [cekk]
1.1.3 (2018-08-21)
Fix document outline [nzambello]
Improved navigation experience when choosing the collection to use [daniele]
1.1.2 (2018-08-02)
Enable other content types to be chosen as the More link [daniele]
Fixed a bug that hid a tile collection with no elements to display. If a user can edit the tiles, now he can see the empty tile. [arsenico13]
Update some italian translations. [arsenico13]
Fix templates for container styles in base view and in empty tile handling [nzambello]
1.1.1 (2018-03-06)
Added Custom “more…” collection field [fdelia]
1.1 (11/10/2017)
Production release [lucabel]
1.0a2 (2017-09-13)
Removed unused css class [cekk]
1.0a1 (2017-03-31)
Initial release. [cekk]
Fix indentation on README.rst
Metadata
Release files for collective.tiles.collection 2.1.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.tiles.collection-2.1.1.tar.gz | 25.3 kB | Without provenance | Details for collective.tiles.collection-2.1.1.tar.gz |
Release files / collective.tiles.collection-2.1.1.tar.gz
| Download URL | collective.tiles.collection-2.1.1.tar.gz |
|---|---|
| Size | 25.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d87eb4f98f3495720fe33c83412b5ee7f64733978a99235569c70a72cd3231ae
|
|
BLAKE2b-256 checksum How to use checksums |
b34f083dd82168546a36ff77010b0031c12fa70f1a5f5f77718bc116d5620494
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.8
|
Security for collective.tiles.collection 2.1.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.