Help Needed: Multiple Finsweet CMS Sliders on One Page | Relume Community
\nThanks in advance.","url":"/x/general/zrxrbk8ndj5g/help-needed-multiple-finsweet-cms-sliders-on-one-p","author":{"@type":"Person","name":"Ali","url":"/members/6b6cbdb0-6475-42fb-86ec-7eb576c48e81"},"datePublished":"2025-07-14T13:37:17.277769+00:00","dateModified":"2025-07-15T18:38:56.455484+00:00","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},"comment":[{"@type":"Comment","text":"Ali without seeing the webflow read-only, and reading the new documentation for CMS slider, I would say you just need the attributes to have the -1 -2 across the board.\n\nCMS Slider doesn't much care about the look of the sliders and whether or not they look the same or not but if in your designers, they are indeed two different sliders entirely (visually) then you'll also need to build out the sliders using different classes AND use the slider-2 etc instance naming for the custom attributes.\n\nHope that makes sense. If you have additional questions around this or issues - please post your webflow read-only as well as the published/staging URL so that I can inspect everything at once and I'd be more than happy to assist in getting this rollin' for you! 馃檶","author":{"@type":"Person","name":"Matt J.","url":"/members/11a88c24-8014-4636-87bf-5b00473e35ac"},"datePublished":"2025-07-14T17:54:53.124817+00:00","dateModified":"2025-07-14T17:55:12.644614+00:00","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0}},{"@type":"Comment","text":"Thank you very much for responding. I tried adding -2 to the slider and list attributes, but it didn't work.\nFollowing is the read-only for the specific page I am working on:\nhttps://preview.webflow.com/preview/eco-elite-inc-website?utm_medium=preview_link&utm_[鈥&pageId=686e9ca7c8ea4b6fe9b4e9da&locale=en&workflow=preview (https://preview.webflow.com/preview/eco-elite-inc-website?utm_medium=preview_link&utm_source=designer&utm_content=eco-elite-inc-website&preview=277bc1f906d04de10e4deb1b1141b171&pageId=686e9ca7c8ea4b6fe9b4e9da&locale=en&workflow=preview)\nI have used the cms slider for the product list section (title = Window Styles That Fit Every Space), and I am currently trying to implement it for gallery section (title = Windows Installed with Care and Precision)","author":{"@type":"Person","name":"Ali","url":"/members/6b6cbdb0-6475-42fb-86ec-7eb576c48e81"},"datePublished":"2025-07-14T19:15:53.341552+00:00","dateModified":"2025-07-14T19:15:53.341552+00:00","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0}},{"@type":"Comment","text":"apologies - I was just referencing the convention, not the full attribute. \n\nAre you using the full attribute based on the finsweet documentation? For example slider-1, list-1, slider-2, list-2?","author":{"@type":"Person","name":"Matt J.","url":"/members/11a88c24-8014-4636-87bf-5b00473e35ac"},"datePublished":"2025-07-14T19:46:30.341346+00:00","dateModified":"2025-07-14T19:47:06.604005+00:00","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0}},{"@type":"Comment","text":"No problem, I understood what you meant..\nYes, I am using it based on the documentation.","author":{"@type":"Person","name":"Ali","url":"/members/6b6cbdb0-6475-42fb-86ec-7eb576c48e81"},"datePublished":"2025-07-14T19:48:06.83134+00:00","dateModified":"2025-07-14T19:48:36.338563+00:00","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0}},{"@type":"Comment","text":"It does mention that the cms slider should work for multiple instances on the same page, but i think it is also saying to modify the script as well. I tried folowing those steps as well but it is still not working. I do think that this is where i might be messing up though (modifying the script). Here is the link to the documentation page (https://finsweet.com/attributes/how-to-set-the-script-tag).","author":{"@type":"Person","name":"Ali","url":"/members/6b6cbdb0-6475-42fb-86ec-7eb576c48e81"},"datePublished":"2025-07-14T22:19:23.265959+00:00","dateModified":"2025-07-14T22:19:23.265959+00:00","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0}},{"@type":"Comment","text":"Oooh! I think your script mod is fine.\n\nI鈥檒l take a look at your implementation.","author":{"@type":"Person","name":"Matt J.","url":"/members/11a88c24-8014-4636-87bf-5b00473e35ac"},"datePublished":"2025-07-14T22:52:36.525867+00:00","dateModified":"2025-07-14T22:52:36.525867+00:00","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0}},{"@type":"Comment","text":"Thank you very much.\nA quick note, I am using Finsweet cms slider, because of the limitation of webflow allowing cms inside a slider. My goal is to design a page that will serve as a template for all the services pages (using components and cms for ease of modification and implementation). Is finsweet cms slider the best way to do it or are there other alternatives?","author":{"@type":"Person","name":"Ali","url":"/members/6b6cbdb0-6475-42fb-86ec-7eb576c48e81"},"datePublished":"2025-07-14T23:03:57.913169+00:00","dateModified":"2025-07-14T23:03:57.913169+00:00","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0}},{"@type":"Comment","text":"yeah, finsweet CMS slider is perfectly suited for this. Will be able to take a look in a few and let you know.","author":{"@type":"Person","name":"Matt J.","url":"/members/11a88c24-8014-4636-87bf-5b00473e35ac"},"datePublished":"2025-07-15T01:11:42.678895+00:00","dateModified":"2025-07-15T01:11:42.678895+00:00","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0}},{"@type":"Comment","text":"Ali its possible that its not working because you have it set to display none on the collection - I can't 100% remember if that matters for CMS slider or not - do you want to remove that and test it out?","author":{"@type":"Person","name":"Matt J.","url":"/members/11a88c24-8014-4636-87bf-5b00473e35ac"},"datePublished":"2025-07-15T18:33:46.503422+00:00","dateModified":"2025-07-15T18:34:02.265926+00:00","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0}},{"@type":"Comment","text":"oh also it looks like you have a slider that doesn't not have an instance on it which could be breaking things - the first slider on that windows page just has \"slider and \"list\" as attribute values, but it should have slider-1, list-1, then the next instance of a CMS slider should have slider-2, list-2, and so on.\n\nRight now you have it\n\nslider, list\nslider-1, list-1\nslider-2, list-2\n\nIn this case it likely doesn't even matter if you wanted to just simply change slider,list to slider-4, list-4 as long as the attributes match.\n\nIt looks like Finsweet also introduced common parent wrapper instances but not entirely sure if that applies to you here or not because of the use of slots and components that you are using.","author":{"@type":"Person","name":"Matt J.","url":"/members/11a88c24-8014-4636-87bf-5b00473e35ac"},"datePublished":"2025-07-15T18:38:54.678304+00:00","dateModified":"2025-07-15T18:38:54.678304+00:00","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0}}]}
Hello,
I am using the Finsweet CMS Slider for a testimonials section following this tutorial, and it worked perfectly for 1 slider per page.
He mentioned for multiple sliders on a page, the slider and list names will have to be changed (slider-1, list-1), ......, (slider-n, list-n). I am trying to implement this part, but it is not working.
Am I supposed to change the class name (of the slider and collection list) as well or just the custom attributes?
Do I have to modify the following script (taken from finsweet's documentation) as well:
Ali without seeing the webflow read-only, and reading the new documentation for CMS slider, I would say you just need the attributes to have the -1-2 across the board.
CMS Slider doesn't much care about the look of the sliders and whether or not they look the same or not but if in your designers, they are indeed two different sliders entirely (visually) then you'll also need to build out the sliders using different classes AND use the slider-2 etc instance naming for the custom attributes.
Hope that makes sense. If you have additional questions around this or issues - please post your webflow read-only as well as the published/staging URL so that I can inspect everything at once and I'd be more than happy to assist in getting this rollin' for you! 馃檶
apologies - I was just referencing the convention, not the full attribute.
Are you using the full attribute based on the finsweet documentation? For example slider-1, list-1, slider-2, list-2?
It does mention that the cms slider should work for multiple instances on the same page, but i think it is also saying to modify the script as well. I tried folowing those steps as well but it is still not working. I do think that this is where i might be messing up though (modifying the script). Here is the link to the documentation page.
Thank you very much.
A quick note, I am using Finsweet cms slider, because of the limitation of webflow allowing cms inside a slider. My goal is to design a page that will serve as a template for all the services pages (using components and cms for ease of modification and implementation). Is finsweet cms slider the best way to do it or are there other alternatives?
Ali its possible that its not working because you have it set to display none on the collection - I can't 100% remember if that matters for CMS slider or not - do you want to remove that and test it out?
oh also it looks like you have a slider that doesn't not have an instance on it which could be breaking things - the first slider on that windows page just has "slider and "list" as attribute values, but it should have slider-1, list-1, then the next instance of a CMS slider should have slider-2, list-2, and so on.
Right now you have it
slider, list
slider-1, list-1
slider-2, list-2
In this case it likely doesn't even matter if you wanted to just simply change slider,list to slider-4, list-4 as long as the attributes match.
It looks like Finsweet also introduced common parent wrapper instances but not entirely sure if that applies to you here or not because of the use of slots and components that you are using.
