Target field is NOT emptied/unchecked when control field is unchecked.

Created on 6 October 2019, over 4 years ago
Updated 8 January 2024, 6 months ago

If an end user makes a target field visible by clicking on a control field then puts values in and then changes their mind and unchecks the control field, the target fields are hidden with the values still there ready to be saved to the node when in fact they're actually not wanted.

I've tried to remedy this problem by setting up a new condition to remove the values from the target field when the control field is set to any particular state. This doesn't work because when it will not 'Add Dependency' when you try to advance to save the dependency.

πŸ› Bug report
Status

Closed: outdated

Component

Code

Created by

πŸ‡¦πŸ‡ΊAustralia the_glitch

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024