You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Dan Klco (Jira)" <ji...@apache.org> on 2019/11/08 15:36:00 UTC
[jira] [Resolved] (SLING-8835) CMS - Make Transformations Based on
Definitions
[ https://issues.apache.org/jira/browse/SLING-8835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Klco resolved SLING-8835.
-----------------------------
Resolution: Fixed
Fixed in [https://github.com/apache/sling-org-apache-sling-app-cms/commit/38833c0315a62ecce65e1ad61a6c2be14cceb8fe] and https://github.com/apache/sling-org-apache-sling-app-cms/commit/0986f22e0247fbad4150ebfbf58dc7c6ced54a95
> CMS - Make Transformations Based on Definitions
> -----------------------------------------------
>
> Key: SLING-8835
> URL: https://issues.apache.org/jira/browse/SLING-8835
> Project: Sling
> Issue Type: Improvement
> Affects Versions: Version App CMS 0.12.0
> Reporter: Dan Klco
> Assignee: Dan Klco
> Priority: Major
> Fix For: App CMS 0.12.2
>
>
> Currently, the transformation library uses the suffix directly to transform the images. This poses a potential issue as users could force the system to create an excessive number of rendered images by providing different variations of the suffix.
> Instead, the transformations should be provided in configuration and then selected by the author. This will also all for caching rendered images.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)