It would be incredibly helpful to have pagination and filtering functionality available inside components .
When working with a large number of instances, handling everything manually becomes very inefficient and messy. This limitation makes it hard to build reusable components that can display dynamic lists, like blog posts or products, in a scalable and maintainable way.
Having filters and pagination natively supported inside components would:
Greatly reduce the need to duplicate logic across pages.
Simplify complex layouts with repeatable data.
Help us build truly dynamic and reusable component libraries.
Hi,
Thanks so much for your report!
We are already working on both problems. The load more problem was reported via ticket, the pagination problem here in the forum:
We’ll update this report about the load more issue as soon as it’s solved.
For the pagination issue, please follow the report mentioned.
Best regards,
timmse
Hi bricks team,
If the elements inside the component have ids (like interactions or filters), they will break after we add the component because their ids will change. Please watch the video below.
Hi @FilWi ,
as for now, I’ll mark this topic as no-bug, because in current implementations, connecting filters to the query loop, that is inside the component, is not supported. You can connect to the query loop that is on the main component element, but not if it’s inside a component.
Thanks for understadning,
Matej
Simple scenario.
I create a store with products I would like to filter.
I have created a filter list and a product card that displays the basic data in a grid. I wanted this product card to be in different places, so I made it a component. When I want to use the target query for the filters unfortunately nothing is displayed in the dropdown list for selection.
Of course, when the product card is not a component (when it is unlinked), this problem does not exist.
You can see this in the reco…
Browser: Chrome 132.0.6834.84
OS: Windows
Hi bricks team,
If we convert a loop item to a component, pagination and filters will not recognize it.
[Screenshot_2]
Hi @Maexxx ,
The way you set up is not supported in Component due to certain technical limitation. (The pagination or Query Result element with target query dropdown unable to identify if your target query is from which particular instance)
You can use the 2 methods below to achieve what you want:
Create a component that includes the Grid Query + Query Result Summary + Pagination. Use property + condition to decide whether or not to output the Query Result Summary or Pagination elements.
[…
I love the show content after nth post
1 Like
Maexxx
July 11, 2025, 10:03pm
2
Yes, pagination needs to work everyhere