Hi,
I have a problem with Attributes V2 List Filter mechanism. I’ve successfully set all of this up - form with radio buttons, search field, etc. and it all works great. In my Collection List, which I filter, I display (as hidden) the category, which is a reference field from my CMS. Both the radio button and the paragraph have fs-list-field = “category”. The filtering then works.
The problem: When I added a new CMS field for second and third category, and display it (also as hidden with the same fs-list-field - “category”), the filtering only works for the first category and regardless of what I do it doesn’t pick up the second nor third one. When I delete the first category paragraph, then it works and picks up the “second” - which now becomes the first element with fs-field-list = “category”).
I had this set up in Legacy V1 Attributes and it worked there, picked up any additional fields with the same fs-cmsfilter-field set. What changed here? Why doesn’t it pick up the additional fields and only watch for the 1st field value?
So, the setup:
- Radio buttons with fs-list-field - “category” and correct fs-list-value corresponding with CMS values
- Three hidden paragraphs linked to each item’s categories. They all have fs-list-field - “category” assigned. When filtered, only 1st paragraph is considered.
Hi @eryk.tomaszek!
We are aware of the issue, we are working on it.
Could you share a read-only link so we can check it out closely?
I apologize for the inconvenience
I’ll let you know when the update is ready!
1 Like
Hi @Support-Pedro!
Thanks for the reply - good thing to know that the issue is known and being worked on. This is a client project I’m talking about, if they grant me the permission to share the read-only, I will send it to you in Direct Message.
Hi @eryk.tomaszek!
We are looking into it, but in the meantime, you can try this:
Define the wrapper (common parent element) of the collection item as fs-list-element="list"
It appears that the filter requires the nested static list to be explicitly defined for all tags to work correctly.
Let me know if that works for you!
Hi there!
Sorry for the late reply. I think what you’re saying is to define the parent wrapper for a static list. I am, however, using the native Collection List connected to a Collection in CMS, which is set as fs-list-element=“list” as the documentation stated.
Hi @eryk.tomaszek!
Yes, you also need to set fs-list-element="list" on the wrapper element that contains your filter fields. We’re working on updating the documentation to make this clearer.
Also, could you share a read-only link so I can take a closer look at your setup? Feel free to DM it to me if you’d rather keep it private.