Re-add reset to default values option

Updated patch from #2 to match latest 8.x-1.x-dev version.

Hello!

Unfortunately this patches were outdated at all. And this functionality was removed from apha1 version, sorry. Probably we will add it again in future. If You really need it, You can create a new task for it and in addition provide a new patch.

Regards Olga.

The current code, at 8.x-1.0-alpha5-1-gb855e9d, seems to be doing what the patch was intending to do.

Here it is what I tried:

• Use a couple of fields, (a) a List (integer) with 3 values(1, 2, 3) as the control field, and (b) a text field as the target field.
• dependency configuration: "The target field is visible when the control field has value...", setting the value to 2
• Add an entity e1 with (a) set to 1, (b) is not visible, and not set as expected
• Edit e1, set (a) to 2, (b) is now visible, add a value, and save; then both fields are set.
• Edit e1, set (a) to 3, (b) is now not visible, and save; then (a) has a value, but (b) does not have the value set on the previous step.

Using the patch I get similar results.

It seems like the patch is not really needed, and the current default behavior is to reset the not visible fields.

Tentatively closing as I could not reproduce the problem.
Please re-open if needed, suggesting how to reproduce the problem.

Looking this a bit more, it seems like the intention of the patch is not about removing the value of the dependent fields, but instead set the dependent field
default value when not visible.

With the patch used, I see the behavior change, and now the default value is set when the dependent field is not visible.
Hence, marking as RTBC now.

Code looks fine, but patch doesn't apply.

Re-rolled against alpha-6, since I need this in a current project.

The part with "Apply reset dependent to default if untriggered behavior" needs to be adjusted for the latest dev version, but it seems quite easy to relocate it.

@thalles, I did a new patch. Can you please have a look? It is not working properly.

I did a new patch for 8.x-1.x-dev. Please review it.
Thanks!

#11 didn't work for me. But I re-rolled 11 with against 8.x-1.x-dev. Please test it out.

Thank you so much @amykhailova,

your patch in #12 works fine for me with beta10 and Drupal 9

Hello!
Patch from #12 doesn't apply ( showing in the image ). Uploading the fixed patch.
The patch is working but I found a problem here: is not being possible to deselect the 'reset' checkbox when editing the conditional field ( when I deselect and save the condition, it is not being saved accordingly).
Tested on Drupal 9.1.6 and Conditional Field 8.x-1.x-dev.

New patch... I didn't attach an interdiff because #14 can't be applied.
Please review.

I have to do a small modification because of if (in_array($key, $exclude_fields) || empty($value))
That is why we can't unchecked the checkbox in the ConditionalFieldEditForm.php.

A new patch...

Hello!
Tested patch from #19 and it worked here. Changing to RTBC.

Tested with Drupal 9.1.9 and Conditional Fields 4.x-dev.

Patch in #19 works for me too.

Thank you so much @paulocs

The #19 patch works for me. Thanks a lot for this :)

Looks good to me!

This fix had worked for me in D8. After upgrading to D9 (specifically 9.2.9), the dependent values are ALWAYS getting reset, even when the dependency is still triggered. Switching back to the 4.0.0-alpha1 release for now, but hoping this gets fixed as the ability to reset has always been an important feature of this module.

I was able to resolve my issue from #27. I figured out the problem was limited to checkbox fields, and reset behavior works as expected when I change the condition from "Checked" to "Value", using the manual entry of values (the widget entry fails).