SOLVED: No possibility of targeting query for filters if it is a component

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 recording.

btw.

  1. just by chance an error crept in on the recording that the unlik component is not working as it should, so I had to refresh the page.
  2. by the way of this post another bug is that copying and pasting items doesn’t work properly. when a particular item is selected you can’t paste anything. when no item is selected, when you click cmd + v it pastes to the bottom.

Maybe it would be a good idea to introduce a new property “value” in the components here. And for example, link it under custom css id. Then it could be referred to which product card to select.

Admittedly, the choice of target query would have to be typed manually and not through the dropdown, or do it another way. But I think this is necessary for the very idea of compnents, so that they can be filtered, otherwise the use of the component in prioduct grids, however, misses the point and you have to stay with the traditional method.

Hello @poziomapl,

thank you for the report. Yep, I could reproduce the issue, where you can’t connect the filters to the query loop defined in the component, and I’ve added it to the bug tracker.

About this one… can you record a video how to reproduce it, if possible, with only Bricks active ?

Thank you.
Matej

Is there a temporary work around for this right now as we are about to start a project that will use components cards in loops and filters.

No known workaround. Also, using components on live projects is not recommended, as they are still experimental.

Best regards,
Matej

1 Like

Hi guys,

We’ve fixed this issue in Bricks 2.0 alpha, now available as a manual download in your account (see changelog).

Please let us know if you are still experiencing issues.

As with any pre-stable release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.

1 Like