Issue with CMS filter with wrong result counter & display of empty section

Attributes
1

Hi there,

I hope someone can assist me with fixing the filtering issues on my site. I’ve spent way too long trying to resolve this with no luck. Hopefully, I’m just missing something simple.

The issue is that my CMS filtering suddenly started behaving strangely in two specific ways:

  1. The item counter doesn’t display the correct number of items after filters are applied. It only updates to the correct number when navigating to the next paginated page.

  2. The “Empty” section is permanently visible after applying filters, even when there are matching results. It should only appear when there are no filter results, but it’s always shown now for some reason.

I’ve already tried several troubleshooting steps:

  • Removed my custom scripts from the site.
  • Tried using Finsweet browser support.
  • Compared my setup with similar filters to ensure everything matches correctly.

Can someone please help me pinpoint the issue and find a solution?

Here’s the live page for reference: Carloop.dk | Showroom for privatleasingbiler

And here is a read-only link to the Webflow site

Thank you in advance for your help!

2

Hi @alexanderhnj2001!

The issue comes from a duplicated fs-cmsfilter-element="list".
If the “car-comparison-column” list is just for reference you can remove the attribute from there, if its needed add a unique number “-x” at the end.

IMG_3959
IMG_39593064×1756 668 KB

Let me know if this solves the issue! :flexed_biceps:

3

@Support-Pedro it worked thank you! I feel like I have tried everything, but this fixed it! A small follow up question regarding the range slider values.

The range slider for “Udbetaling” does not show filtered cars if it has a value of 0 “udbetaling”. This is something there has been an issue for the past 6 months. We only have one car which has the value of 0 on this, but there might come more in the future.

Is this something you know about why range slider behaves in this way? And is there an easy fix for it?

Thank you in advance!

4

There are two options to solve this issue:

  1. This problem will be solved in Attributes V2, which is set to launch soon.
  2. I can write a custom script to fix it.

Let me know which option works best for you.

5

@Support-Pedro thank you for your quick answer and your help! I think I’ll just wait for the V2 launch. Does “soon” mean weeks or months, or can you give me a time estimate in general?

Again thank you in advance.