Community forum for knowledge and support

Updated last year

Finsweet Filter Issues and Wedding Deadline

At a glance

The community member is having issues with a filter they are trying to implement on their Webflow site before their wedding. They have tried various approaches, such as using the fs-cmsfilter-range option, adjusting the field identifiers, and removing range attributes from the CMS linked fields, but the filter is not working as expected. The community members have tried to troubleshoot the issue, with one suggesting lowercasing the field identifiers and another noting that the filter and filter attributes are complex to implement. Ultimately, they discovered that the issue is likely a bug with Finsweet, the tool they are using for the filter.

Useful resources

Not getting any feedback from finsweet and I need this site finished today before im off for my wedding.. has anyone built a similar filter with min/max values?

I need to set a from/to value for price, beds, baths, & car spaces, but using fs attributes filter with the 'fs-cmsfilter-range' option just doesnt work at all for me.
I've tried with and without the fs-cmsfilter-range=“to/from” attribute on the select fields only or select fields plus the field in the collection list, ive tried with and without a hidden 'from' value in the collection list for all 4 filters, ive tried with and without the $ sign in price values.

For price, the results are all over the place, some above some below

for beds/baths/car spaces, the best ive got it to achieve is it filters the last select field (max), ie if i choose from 2-4 beds, it will show me only results with 4 beds.

https://inndeavor.webflow.io/rent

https://preview.webflow.com/preview/inndeavor?utm_medium=preview_link&utm_source=desig[…]a9463e87f0&pageId=65b70053c3edfa589722f77c&workflow=preview

M
J
19 comments

I've added the automated support query parameter to your published URL and there are several errors being returned back. I would resolve those first, and then we can go from there.

https://inndeavor.webflow.io/rent?fs-attributes-support=true

Thanks , I've cleared a few, got it down to this error which shows for all 4 indentifiers (PRICE, BEDS, BATH. CARS)

But the attribute IS on the select field

Alright, awesome, let me open up your project again and take a peek. Let's knock this out man!

I did just publish some changes in the last few minutes

this might be really stupid, I dont know. But can you try lowercasing all of "PRICE" > "price" - Javascript can be pretty finicky. No promises, it likely makes absolutely no difference.

had the same thought in the back of my mind but ignored it, ill try it

yeah its simple enough, worth a try

also, I would try removing the range attributes on the CMS linked fields

those attributes are only meant for the filter inputs - but the CMS linked fields are the outputs.

For both beds and bath, you have different field identifiers. For the min you have BATHS-MIN and then just BATHS (again, lets keep them lowercase, just in case).

yeah lets do that and see what the automated support spits out from there

yep noticed the indetifiers just fixed all of those

or maybe it'll work 🤷

ive made all lowercase with no change, ill remove the range attributes from the linked fields

im mostly expecting to lower some of these errors more than anything at this point - filters and filter attributes are literally the most complicated pieces you can add to a site - and then on top of that we have a range to deal with so yeah....we'll get it done though. 💪

all identifiers are now lowercase
range from/to attributes removed from linked fields
still getting the same error in support tool, saying the field attribute is not on the select field

now it wont show a result for price unless you choose the exact amount in the to field (choose $1500 to see)

Testing with bathrooms fields

If you choose a value for min only, it will filter correctly
If you choose a min & max, it will only show exact matches for the max value
if you only choose a max, it will do the same as above

Just so no one thinks I left my pal Jake stranded here...we took it to the DMs and discovered its likely a bug with Finsweet, which is quite unfortunate. Go marry the girl Jake! 🎉

Add a reply
Sign up and join the conversation on Slack