ideas
ideas copied to clipboard
statamic
FR: Option to let conditions also work with fieldsets.
It would be really helpful if it is also possible to set a condition for a fieldset in the CMS. It is now only possible on normal fields.
Example: If toggle = true, show this fieldset. If toggle is false, show another fieldset.
When I try this code my CMS blueprint will eventually override this piece of code when I save it.
-
import: typing_header
if:
animated_header: 'equals true'
A workaround for this would be to add the conditions to each field inside the fieldset.
Bumping because I don't believe that workaround is suitable. A fieldset could be (and likely is) used in multiple places. Sometimes the condition that would be checked in one blueprint differs from another.
In my case, I use a fieldset for a specific component that can be used in content, so it is linked in Bard as a set. But also may be used outside of content, so it is linked in the blueprint for the page. I would like it to conditionally only show if a particular toggle were on in the page, but unconditionally show if it is added as a set to bard.
I just spent about 30min going down a rabbit hole trying to figure out if something was possible and it appears it isn't - I thought I would share here in case relevant.
Basically I'd like the ability to hide a set in a replicator without "removing it from play".
The use-case is I have 10 variations of a hero component with slightly different fields (I know I can use conditionals but hear me out)...
If I was to create sets for each of the variations then hide all but the default hero, I could add a select element with the handle type to allow dynamically changing the set type, including to the hypothetical non-visible ones.
Here is a demo
The result is a pretty nice experience for users!!! You can see no data is lost when switching. Fieldsets mean configuration is rather DRY and it's easier to modify than conditionals.
Unfortunately you CAN'T hide a set (correct?) so this means, 10 variations in the replicator... which is what I wanted to avoid. Back to a select that isn't named type and conditionals for now.
But if we could add conditions to a set (or just hide them) I can see this having potential.
Yes to this!
Accidentally duplicated this – here’s my two cents of how it would be handy:
https://www.loom.com/share/df6f8dfac42d4ada97683ed778916f0e
My workaround is wrapping each imported fieldset into a Grid with max_rows and min_rows set to 1, hide_display to true, reorderable and fullscreen to false
@jasonvarga Any idea when this will be fixed? Because the workaround you provided isn't a full proof option.
@jasonvarga Currently, I am already programming on a solution. The only problem I am running into, is storing the conditions within the CP (Vue JS). Is this easy for you to make? Because I can already add a condition in the YAML files which the back-end code reads. See screenshot below for an example YAML structure.
Update: I've created a pull request for this request: https://github.com/statamic/cms/pull/8690
+1, tbh we are urgently missing this in some projects.
simply adding the conditions to each field in the fieldsets is not a workaround which I feel is sufficient – imho a fieldset should be agostic to the context it will be referenced in :)
I added some additional ideas in another discussion (before I found this issue): https://github.com/statamic/cms/discussions/9836#discussioncomment-9477079.
Deals with fieldsets, sections, groups and the idea to add the logic to a controlling field instead to the reacting fields.
I have the exact same problem. When I use a fieldset in a blueprint, there is no option to apply the usual conditional show or hide logic. The same is true for sections.
To use a group field to wrap a fieldset or a field adds unnecessary complexity and somewhat thwarts the purpose of fieldsets to make using fields easier, and it prevents fields/fieldsets from being moved around easily individually because they are stuck in a group. (Group fields also add superfluous labels on the blueprint, especially if used for just one field or a fieldset with just one field.)
If it were possible to give them both (fieldsets and sections) access to the conditional view/hide logic, that would be a big plus in terms of usability!
I'm not sure if it's technical feasible, but wouldn't it be better if we had an option in the steering/controlling field to decide which other fields (identified by their handles) should be shown or hidden? By way of a list of handles?
For example: If you have a toggle, offer a select option there to create a list of handles of other fields, fieldsets and sections which should be conditionally hidden.
That would have the added benefit that it's no longer necessary to duplicate the same kind of logic in a bunch of fields (and no, putting them in groups is not always an option if they are sprinkled throughout the blueprint.)
