I have a question regarding the filter attribute in V1 in comparison to this function in V2.
For my client I implemented the filter attribute in order to filter hundreds of blog-articles. Unfortunately the complete list of teasers with pictures had to be loaded by the browser upfront to be able to filter them.
Is this still the case in V2?
Hey @kopitz, yes this is still the case for V2.
Do you have an idea for a workaround?
to for example:
@kopitz, could you share a read-only link? I’d like to see the structure of your current setup, maybe we can think of something.
Thanks for your help!
You will find an example in “Themenfelder"
@kopitz we may need to restructure the whole collection. An idea I had was to set the image src to a data attribute like data-src, then use the API to set this src to the image element on the collection list just before rendering the items.
However, we cannnot access the src url for the image fields, you’d have to manually add a new field on the collection that stpores this value so we can properly link it to an attribute.
The native option would be to enable pagination count, this way Attributes can optimize your load based on your page count.
That sounds promising. I will try that and let you know. Thanks a lot for your help!
