[MGNLWIKI-52] Image variations: improve integration of imaging module Created: 06/May/10  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Wiki Markup Renderer (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

With MGNLWIKI-51, we have semi-hardcoded support for image variations; it's hardcoded to use website images, and the /.imaging prefix. The imaging module should provide some sort of link builder to avoid these workarounds.



 Comments   
Comment by Antti Hietala [ 03/Jun/10 ]

Voting for this issue and providing an example: Generating a clickable thumbnail for DMS image

  • Store images in the DMS so they can be easily reused in many pages. (works)
  • Link to a DMS image with a text link. (works) Syntax: [Link label|/dms/my-image.png]
    Note that when clicked, the browser treats the target image as a downloadable item. It shows up in the Downloads dialog instead of simply opening in the browser window like an attached image. MIME type issue?
  • Ability to generate a thumbnail from the DMS image. Thumbnail path is not built correctly.
  • Ability to choose whether the target image simply opens in the browser window or is displayed in a lightbox.
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 11:14:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.