Description
I have a quick look style on my home page with three custom radio buttons to choose from. My collection list is directly below. When I select a radio button the entire list disappears. Site URL
Required: Please provide a staging/production URL where we can see the issue
Steps to Reproduce
- Using the lumos framework, I created properties for the attributes. Added the attributes to the form, collection list and radio buttons
- Turned my collection list into a component
- Finished the design. I do think the values for my radio buttons are off. Not sure if I named them correctly. I am using the hidden (none) paragraph in my card component as my list field connector.
…
Expected Behavior
Once published, when I click the protected button, all the items with protected show up. Same with scheduled and available. I am using the paragraph in my card component as my list field connector.
Actual Behavior
when I click (whichever) all my items disappear
Video/Screenshots
Required: Please provide a short screen recording showing the issue
Additional Context
- Browser: [e.g., Chrome 120, Safari 17]
- Device: [e.g., Desktop, iPhone 14]
NDA Notice: If you’re under an NDA, please feel free to send us a Direct Message/Email with the above information.
Hey @jillbascome! You’re really close to having this work 
The core issue is that each radio input has fs-list-value=“name” — that’s a placeholder the Lumos framework inserted but never replaced with your actual CMS data. When you click a radio, the filter looks for CMS items where the status field contains the literal text “name,” and since nothing matches that, everything disappears.
The fix is straightforward — replace “name” with the exact text your CMS status field outputs for each item. Since the paragraph inside each card already has fs-list-field=“status”, the filter will compare the radio’s fs-list-value against whatever text that paragraph renders on the published site.
Here’s what to do:
-
Open your Webflow CMS collection and note the exact text stored in the status field for each item — things like Protected, Scheduled, Available for import. Casing and spelling must match exactly.
-
In Webflow Designer, select each radio button and update fs-list-value from “name” to the matching CMS status text:
fs-list-value="Protected"
fs-list-value="Scheduled"
fs-list-value="Available for import"
(use your actual CMS values here)
-
Remove the fs-list-field=“” attribute from the h3 heading on your card — it has an empty value right now, which can interfere with filtering.
-
Delete the stray attributes on your radio inputs — protected=“value”, scheduled=“value”, and available-for-import=“value” aren’t valid fs-* attributes and can go.
-
Publish and test on your live staging URL — Attributes don’t run in Designer or preview mode.
Also worth a quick check: make sure your CMS items actually have content in the status field, since an empty field won’t match even with the correct setup.
Let us know how it goes after those changes — if things are still disappearing after publishing, drop your staging URL and we’ll dig deeper 
Hi Finn,
I am not sure where the attributes on the radio inputs are but I am assuming the “check ui” component within lumos component card (see screenshot). And because the new attribute for value was made, I should delete the one that came in the lumos component? Also the content I am trying to draw from is the badges status field which is a reference field that connects to badge status cms containing the name and the badge icon. I was using it that way to filter the badge icons on the cards, which is working using the conditionality feature. I am a little turned around…so to reiterate (for my own understanding)…where are the stray attributes and how do I use the name from the badge status reference field to filter the produce varieties cms. I hope this is clear…(I am spun around a bit with the new features from everyone).If this is a lumos question please let me know
