[MGNLIMG-79] No longer possible to override outputFormat Created: 02/Mar/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Imaging
Component/s: image operations
Affects Version/s: 2.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Richard Unger Assignee: Magnolia International
Resolution: Won't Do Votes: 0
Labels: verify
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia EE 4.4.2


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Whereas before imaging 2.1 (in Magnolia 4.3.8) it was possible to set the outputFormat for a generator chain, the outputFormat node is seemingly ignored in imaging 2.1.

It seems that the output format is now always taken from the source image.

This makes it impossible to override the output format for a given generator, which is a feature that we are using.

Note also:

it would actually be preferable to set the outputFormat on the variation definition (in the theme) rather than for the whole generator chain.
In this way magnolia would be flexible - different outputFormats could be specified for different variations, and if none is specified, the source image format is used.

That would be ideal.



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 02:12:04 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.