Question #2215
closed
Feature #1931: Display images
Details View: Too many images break the view
Added by Moritz Großfurtner 10 months ago.
Updated 5 months ago.
Description
For entities that have a lot of images connected to them, the image viewer breaks.
At the moment about 10 images is the maximum. It might have something to do with the "Carousel" component.
Examples can be found by navigating to a license type as those often have a lot of images associated with them, but a concrete example would be entity 20158
on the demo dev site using data from the Thanados project.
- Status changed from New to In Progress
It should be mostly fixed. However, for performance reasons for entities with a lot of images, e.g. the licences type, the detail view would load all the images at once, potentially slowing the site down quite a bit.
To remedy this, I would have progressively loaded the images as the user scrolls through them. In the current implementation, this leads to a rather abrupt jump to the next slide, rather than a smooth transition. Is that something we care about at this time in development or should we leave that for a separate issue? Or is it even relavant since most entities won't have that many images anyways and we can ignore the performance for those cases?
I think there will be no (non-type) entity in the near future which has this amount of images assigned to it. And I think, for Types, there is no need to show the images in a slider.
Did you test it with 50 images? How fast is it?
Thanks for the feedback, that makes sense. I have not yet tested it for 50 images, but I believe that should not cause any problems. I'll test it out and if everything works as expected, implement the fix without the progressive loading.
- Target version changed from 0.4.0 to 0.7.0
- Assignee changed from Moritz Großfurtner to Olivia Reichl
- Tracker changed from Bug to Question
- Status changed from In Progress to Closed
- Target version deleted (
0.7.0)
- Found in version deleted (
0.3.0)
It seems to work in the version 0.5.0 and the issue can't be reproduced.
So the issue report was turned into a closed question. Please contact us, if you still encounter some problems.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by