Do not hide this Collection List . If it is set to display: none , it will not be shown in the parent list. If the list being visible in the Designer is annoying, you can add a wrapping div and hide it.
Hey @Support-Pedro, Thanks for looking into this. The collection highlighted in your screenshot is an old nested CMS that I’m trying to replace. I have also tried it by removing this old nested collection. The new nested element is inside a div called filter_nest which is hidden.
@Support-Pedro Can you provide additional support? I have since deleted the old nested cms and added and removed the attributes multiple times based on documentation and im still not having any luck. Thanks
I took a look back at your page, and I noticed that you are now using the Webflow Native Nested List method. The issue is that Webflow Native Nested Lists are limited to 10 items.
In your “Construction & Home Services” Collection list, you have 13 nested subcategories, so 3 items are not being displayed on your nested list.
I recommend you use the default List Nest method to nest all your category checkboxes correctly.
If you don’t mind using the Default Method, try this setup:
If you have any specific reason to use the alternative slug method, please let me know, and I will work on a solution with that method.
I also noticed that when you select a filter, the filters list also gets filtered. We can solve this issue by adding fs-list-instance="filters" on your element with parent-cat_clist class.
If you have any questions about this setup, just let me know!
Thanks @Support-Pedro for the thorough walkthrough. I apologize for the confusion and the current state of the read only link. Client pushed the changes live before this issue was solved so I had to revert back to the webflow native nesting.
The goal is to switch to the slug method to allow the client to add as many sub-categories they want without limitations.
The setup will work with either nesting option. Since the collection is not that big, I recommend using the default nesting method, as it avoids the double data entry required by option #2.
Hello again @Support-Pedro I created a sandbox page to further test this nesting behaviour, which can be found here. Once again, I have removed all attributes and started fresh, tried no space on slugs and used one slug as seen in the first tab “Places to Stay” and still having no luck.
Update the attribute on your CMS Field Slugs element:
Currently, you are using fs-list-instance="sub". It should have: fs-list-nest="sub" and fs-list-element="nest-slugs".
