[MGNLSTK-1515] Make the list of STKAssetRenderer's allowed image types configurable Created: 09/Nov/15  Updated: 09/Feb/17  Resolved: 09/Feb/17

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Richard Unger Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: blocked, devwl, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
dependency
depends upon MGNLIMG-177 CachingImageStreamer might store inco... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:
Sprint: Basel 50
Story Points: 5

 Description   

With the move to magnolia 5 we are finding that many of our images which used to be just fine are not rendering correctly in magnolia 5.

Reason is that these images have different mime-types:
image/x-png - the mimeType used by PNG before the standard image/png was registered
image/pjpeg - mimeType used by Internet Explorer when uploading progressive jpegs

In Magnolia 4.4 these didn't cause any problems.
In Magnolia 5 the new Assets stuff can't deal with them.

The problem is (initially) with info.magnolia.module.templatingkit.dam.STKAssetRenderer
This defines a set of allowed MimeTypes, it is too restrictive.
Please add the pjpeg and x-png image types.



 Comments   
Comment by Philip Mundt [ 01/Jul/16 ]

Doesn't work, sry...

Comment by Jan Haderka [ 07/Jul/16 ]

Blocked until provided with sample images with said mime type.

Generated at Mon Feb 12 07:37:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.