Up until last week, visible_if could be used to show and hide resource inputs (product, collection, page) as long as the conditional was based on the value of a supported input type (checkbox, select, etc). Not being able to use visible_if to toggle between collection and product_list inputs would …

Update: This appears to be specfic to /blocks schema. These settings will save and work correctly in seciton-level settings and classic block settings.

Running into same problems as you with my /blocks which were working fine with the visible_if until yesterday! Super frustrating.

@Gideon We don’t allow conditional resource settings, this is an intentional limitation as it conflicts with closest.<< resource >>. The fact that it worked up until now was a gap in our validation. You can find the list of supported conditional settings here . Update: This appears to be specfic to…

Not being able to gatekeep those is big loss for merchant usability imo. I think the visible_if is great at making the schema settings in theme editor more merchant friendly and this feels like big loss on that regard.

I understand why it would be problematic to parse a conditional statement that depends on the value of a closest resource. This conditional uses a select input. The docs do not differentiate between settings that can be used in a conditional statement and input types that can be shown/hidden. It s…

Here is a more concrete example: This should not work. It requires context to resolve the value of closest. { "type": "checkbox", "id": "checkbox", "label": "Checkbox", "visible_if": "{{ block.settings.product != blank }}" }, { "type": "product", "id": "product", "label": "Product", …

@Gideon There are two separate restrictions to know: Conditional settings can’t access runtime context or values from resolved data sources. This is aligned with what you are saying. Only the inputs listed under The following settings support conditional settings on that page can be shown or h…

@misha with all due respect point number 2 is absolutely ridiculous. I can accept that we can’t use the value of a resource input for another setting’s visible if condition. However, the fact that resource inputs are completely blocked off from visible if, is just insane. I don’t mean to ask too mu…

Make visible_if work for all settings, add a warning in the documentation and leave the specifics to us, that’s our job. The feedback is real and the requirement is clear, make it happen please ! There is no point in having this visible_if property if we need to tiptoe our way using it.

I have raised this issue for a long time but now there is a clue and they have not done it properly.

Using visible_if to show/hide resource inputs

Online Store and Theme Development

PaulNewton October 21, 2025, 1:54am 20

tangentially related about managing placholders in themes Horizon theme placeholder images

Topic		Replies	Views
Conditional settings feedback Online Store and Theme Development liquid	4	193	December 9, 2025
Add support for visible_if for resources Online Store and Theme Development theme-editor	1	75	January 27, 2026
Conditional settings in the theme editor Changelog	0	82	May 21, 2025
Are there more advanced visible_if conditional logic techniques we can use within the section/block schema? Online Store and Theme Development liquid , theme-editor	2	185	September 22, 2025
Visible_if doesn't seem exactly compatible with dynamic data sources Online Store and Theme Development liquid , theme-editor	7	670	August 4, 2025

Using visible_if to show/hide resource inputs

Related topics