Bug #2755
closed
Shahi presentation site ignores set main image
Added by Gosia Lenko 9 days ago.
Updated about 17 hours ago.
Description
I would like to draw your attention to an important issue, particularly relevant for the collections but not only.
The main image displayed on the front end does not correspond to the image set as the main image in the back end. When a record or collection contains multiple images, the system appears to select a random image—or possibly the most recently added one—as the main image, instead of the image explicitly designated as such.
I am not certain what causes this, but it is problematic and makes the front end unattractive.
Screenshot for examples added (collection and regular object, front and back end).
Files
- Subject changed from Main image displayed on the front end not corresponding to the image set as main in the back end to Shahi presentation site ignores set main image in backend
- Status changed from New to Assigned
- Assignee set to Olivia Reichl
- Target version set to 1.1.0
Thank you Gosia for the detailed description and the screenshots.
@Olivia Reichl:
According to Bernhard the information which image is set as main image should be available via the API.
But because this is a legacy frontend (developed by Andi) I'm not sure how easy it will be to update it accordingly.
I assigned this to you as our frontend expert but please let us know, in case you need support for this.
- Subject changed from Shahi presentation site ignores set main image in backend to Shahi presentation site ignores set main image
- Status changed from Assigned to Resolved
- Assignee changed from Olivia Reichl to Katharina Wünsche
The issue should be fixed now. @Gosia Lenko, could you check if the images are now displayed as expected when you get a chance? Thanks in advance!
- Status changed from Resolved to Closed
- Target version deleted (
1.1.0)
I checked it with:
and it seemed to work but please report if it is not working somewhere else.
A very big thank you to Katharina for solving this.
I'm closing this issue and removing the version because this is not part of the current frontend development.
Also available in: Atom
PDF
Updated by 
Updated by 
