Within unlinked components we can set conditional visibility based on whether a specific CMS field "is set." With components we only have conditional visibility based on "toggle" fields. I'd like to set an icon button to appear only if a specific link "is set" and hide if not set.
Patrick Foley
.svg){kind=logo}
And here I need to come back again. Why is this even inconsistent to begin with? Please unlock the potential power of components.
And it doesn't work for dropdowns as well, unfortunately.
And the worst thing is, you can't even invert a toggle!
For example: If I want an element to be HIDDEN instead of visible, when a toggle is set to true – not possible. Really annoying because it seems like such a small thing. Now I have to make to switches in the cms collection which makes the UX worse for the end user.
YES! Why not bring the power of conditional visibility over to the component properties??!
It's literally so simple: make the same settings for conditional visibility available at "normal visibility" for components.
This is very crucial. For example, I have a 'New' tag that appears on the blog post card for up to 15 days from the publication date, but I can't use components because the conditional visibility is locked for toggles.
I'm fairly amazed this hasn't shipped– it seems like it would be low effort and high return. With a site that has a lot of CMS content and uses collection lists with a large amount of conditional visibilities to display it, not having this is really curtailing the actual power of using components.
An easy example is with product tiles. I can't use components if I want to have something like a 'new' tag for recent products published in the last 14 days. There's a lot more use cases, but something as simple as that is preventing me from using components in a meaningful way and I still have to update every instance of product tiles.
I would love to see this