[MGNLSTK-540] Teaser referring to image gallery does not show any image Created: 04/Dec/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: paragraphs
Affects Version/s: 1.2
Fix Version/s: 1.4.x

Type: Bug Priority: Minor
Reporter: Christian Ringele Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLSTK-541 Teaser refering to faq page does not ... Sub-task Closed Philipp Bärfuss  
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Since STK 1.2 the teasers pointing to pages retrieve the teaser image from the first image in the content.
When a teaser refers to an image gallery, no image is retrieved.
I guess because the images shown in the image gallery is not in the gallery's content (in DMS).

I think this looks quite bad, when all other referd pages a image is retrieved, but from IMAGE gallery not

See:
http://demopublic.magnolia-cms.com/demo-project/multimedia.html#main

I think it makes it very hard to have a consistent behavior on a site, now that the images used for a teaser come automatically from the content of a page.
With the loss of the definition on page-info level, the only way to manage the used image for the teaser on the target page is using a image within the page header.
The definition on the 'teaser overwrite' is not really a possibility, if you want top make sure, that all teasers pointing to a page display the same image. And for all automatic selection of an target page, it's not possible to define the used image on the content of the teaser, it must be defined on the target page. For example for the myMoneyWorks I created a teaser pointing to a section, and just randomly a child page is used wothn the teaser. This implementation would be much more complicated now, and especially much more confusing for the author.



 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 07:28:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.