Plone.app.tiles

Latest version: v4.0.1

Safety actively analyzes 613705 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 4

4.0.2

------------------

- Nothing changed yet.

4.0.1

------------------

- Use ``ScalesDict`` instead of ``PersistentDict`` to store scales in persistent tiles.
This avoids ``plone.protect`` warning about write-on-read.
Migrate the storage on-the-fly, just like ``plone.scale`` does.
[maurits]

4.0.0

------------------

- Add support for Plone 6 on Python 3.10 and 3.11. [maurits]

4.0.0a2

--------------------

- Register our demo tiles when you explicitly load ``demo.zcml``.
Add them to the list in ``plone.app.tiles`` and ``plone.app.mosaic``.
[maurits]

- Accept a fieldname in ``get_original_value`` in our scaling code.
Needed for recent plone.namedfile versions.
[maurits]

4.0.0a1

--------------------

- Register our own ``IImageScaleFactory`` factory for persistent tiles.
This fixes scaling images on tiles when the tile does not have the workaround of defining a property for the image field.
[maurits]

- Register our ``AnnotationStorage`` as ``IImageScaleStorage`` factory.
We require ``plone.namedfile >= 6.0.0a2`` for this.
Fixes `issue 48 <https://github.com/plone/plone.app.tiles/issues/48>`_. [maurits]

- Drop support for Python 2 and Plone 5.1.
Plone 5.2 and 6.0 are supported, on Python 3.
See `issue 49 <https://github.com/plone/plone.app.tiles/issues/49>`_. [maurits]

3.3.0

------------------

Features:

- Define ``download`` and ``display-file`` views that work for tiles.
The original views in ``plone.namedfile`` cannot find the tile data.
[maurits]

Bug fixes:

- Fixed getting original image from tile.
Until now, the ``images`` view tried to get the field from the tile instead of the tile data.
This only worked when you had explicitly added a property with this field name on the tile.
[maurits]

Page 1 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.