Easy "one of" multiple value field state condition

Open on Drupal.org →

Created on 5 August 2024, 3 months ago

Updated 30 August 2024, 3 months ago

Problem/Motivation

A client has used the conditional field logic successfully for several years. They just requested that the "value of" condition be expanded to "one of" so that it could match against one of a range of items.

I tried doing the "Pattern" option and did *partialstring* but it was unreliable, and also not intuitive for less technically savvy content staff.

Steps to reproduce

Have multiple fields on a form, including a text field, a checkbox, and a radio (or similar multi-value field) with multiple items.
Add conditional logic on the text field.
Add a "visible" state.
Make the state require all options present.
Add a condition that looks for the checkbox field to be checked.
Add a condition that allows the radio field to be one of a subset of items.

Proposed resolution

Either extend the existing "Value of" condition to allow multiple selections, similar to a tag autocomplete field, or add another "One of" condition that can select multiple values.

Remaining tasks

Work out the best approach.

User interface changes

It is possible to easily select multiple items (a subset) from the available options on a multi-value field when adding a state condition for a field.

API changes

TBD

Data model changes

TBD

✨ Feature request

Status

Active

Version

6.3

Component

User interface

Created by

🇺🇸United States DamienMcKenna NH, USA

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Comments & Activities

Issue created by @DamienMcKenna
Comment 3 months ago →
🇺🇸United States DamienMcKenna NH, USA
The site is still on 10.2, I wonder if upgrading to 10.3 to get 🐛 #states not working correctly when built from a logical combination of multliple fields Fixed might help?
Comment 3 months ago →
🇺🇸United States DamienMcKenna NH, USA
FWIW I ended up achieving this using an extra container that had the checkbox condition, then the fields inside it had the multivalue condition. It worked, though was a little messy at the CSS layer to make it look correct. But it worked.
Comment 3 months ago →
🇺🇸United States DamienMcKenna NH, USA
My workaround doesn't work properly - dependencies on nested fields are triggered even if a parent field prevents them from being displayed. Argh.
Comment 3 months ago →
🇺🇸United States DamienMcKenna NH, USA
Never mind #4, it turned out to be a problem in our custom code - we had custom validation logic that would set a default value for certain scenarios, I had to change the custom logic to run before the default validation callbacks rather than afterwards, then it worked.

So all good, this workaround seems to be workable for now.
First commit to issue fork.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024