Struggling with Blog 19 Component and Finsweet Attributes Integration

·Feb 12, 2025 01:14 AM

Hey guys, I'm struggling to get the blog 19 component to work with the finsweet attributes so the filtering on page isn't working. I'm guessing its not correctly implemented (their documentation isn't super easy to follow for me). Read only file. Any ideas? Thanks in advance!

14 comments

· Sorted by Oldest

Matt J.
·
Andy S. you mind also sending the published URL (webflow.io) so I can see it not working
Matt J.
·
but I can see why already too, but I can show you a trick once you send the URL
Andy S.
·
Matt J. Sure thing, here you go: https://www.effectivegiving.ie/charities
Andy S.
·
Or you mean this one? https://effective-giving-ireland-aca627.webflow.io/charities
Matt J.
·
yeah either one is fine for what we gotta do here
Matt J.
·
Andy S. so going the finsweet route is the most complicated way to go about it. Are you against just turning those into links and taking the user to a page that lists out the blogs within that category? I'm trying to find an example
Matt J.
·
it would be identical to this actually https://webflow.com/blog
Matt J.
·
but yeah, you can use Finsweet's self-support tool, which is just this query parameter you use at the end of your published URL and follow the prompts, and it will tell you what is missing: https://effective-giving-ireland-aca627.webflow.io/charities?fs-attributes-support=true
Matt J.
·
With that said, it looks like Finsweet CMS Filters is wanting to have the filers be a form, so you'd have to convert the first CMS collection list you have now to include form elements, not link elements.
Matt J.
·
You will also want to make sure that you are putting the attributes on the CMS collection LIST - right now, you have the attributes on the CMS collection list WRAPPER. Additionally, you've included the default "IDENTIFIER" value. In your case, you'll want to change all instances where that is in the Finsweet documentation to be simply "category" and make sure that its identical across all instances where you define that value. I'm seeing several missing attributes, which you can also see by that link above.
Matt J.
·
I'd say once you've resolved those issues, we can probably check in with the self-support tool again to see what else there might be, and go from there but those were the big things I saw in my quick glance.
Matt J.
·
But again, i think we might be over complicating this implementation.
Andy S.
·
Thanks Matt J. I'm going to explore the simpler option similar to the webflow example. If that won't do it I'll come back to Finsweet later and see if I can get it to work following your guidance. Appreciate the support! 🙌
Andy S.
·
Might also be worth updating those components so the filters are made with forms rather than links just to help mitigate confusion when others try and use them with the finsweet power ups.

Matt J.
·
Andy S. you mind also sending the published URL (webflow.io) so I can see it not working
Matt J.
·
but I can see why already too, but I can show you a trick once you send the URL
Andy S.
·
Matt J. Sure thing, here you go: https://www.effectivegiving.ie/charities
Andy S.
·
Or you mean this one? https://effective-giving-ireland-aca627.webflow.io/charities
Matt J.
·
yeah either one is fine for what we gotta do here
Matt J.
·
Andy S. so going the finsweet route is the most complicated way to go about it. Are you against just turning those into links and taking the user to a page that lists out the blogs within that category? I'm trying to find an example
Matt J.
·
it would be identical to this actually https://webflow.com/blog
Matt J.
·
but yeah, you can use Finsweet's self-support tool, which is just this query parameter you use at the end of your published URL and follow the prompts, and it will tell you what is missing: https://effective-giving-ireland-aca627.webflow.io/charities?fs-attributes-support=true
Matt J.
·
With that said, it looks like Finsweet CMS Filters is wanting to have the filers be a form, so you'd have to convert the first CMS collection list you have now to include form elements, not link elements.
Matt J.
·
You will also want to make sure that you are putting the attributes on the CMS collection LIST - right now, you have the attributes on the CMS collection list WRAPPER. Additionally, you've included the default "IDENTIFIER" value. In your case, you'll want to change all instances where that is in the Finsweet documentation to be simply "category" and make sure that its identical across all instances where you define that value. I'm seeing several missing attributes, which you can also see by that link above.
Matt J.
·
I'd say once you've resolved those issues, we can probably check in with the self-support tool again to see what else there might be, and go from there but those were the big things I saw in my quick glance.
Matt J.
·
But again, i think we might be over complicating this implementation.
Andy S.
·
Thanks Matt J. I'm going to explore the simpler option similar to the webflow example. If that won't do it I'll come back to Finsweet later and see if I can get it to work following your guidance. Appreciate the support! 🙌
Andy S.
·
Might also be worth updating those components so the filters are made with forms rather than links just to help mitigate confusion when others try and use them with the finsweet power ups.

Struggling with Blog 19 Component and Finsweet Attributes Integration | Relume Community