SOLVED: Converting a query loop to a component removes the connection to pagination and filters

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.

1 Like

Hi Hosein,
Thanks so much for your report!

We are already working on being able to use filters and pagination in combination with components. It already works in our dev version, so I assume that it will be implemented soon. We will update this thread as usual as soon as this is the case.

Best regards,
timmse

Thank you timmse, great. Good luckđź’Ş

Hi Hosein,
We fixed this issue in Bricks 1.12.2, now available as a one-click update in your WordPress Dashboard.

Changelog: Bricks 1.12.2 Changelog – Bricks

Please let us know if you are still experiencing issues.

Best regards,
timmse

2 Likes

This is not really fixed in 2.0 beta.

While it might show the proper Query selected “Article xyz (instance)”, the instance is not found, which Bricks also shows in backend. And it doesn’t render it on the frontend either.

I have a simple component which loops the article cards and has the query exposed as Component parameter.

Of course, also the “Query Results Summary” element does not work then.

The problem should be fixed in the next version - at least I can’t reproduce what you describe at the moment. Please let us know if the issue persists and provide us with detailed steps to replicate it.

Then I am waiting for the next bugfix release.