I have encountered an issue with conditional_fields after upgrading from Drupal 9 to Drupal 10. The problem concerns a content type which has a required field that is only visible when another control field (a checkbox in this case) is checked. Prior to the update, checking the checkbox would reveal the required field for filling out, while leaving it unchecked would keep the field hidden and allow the node to be saved without any issues. However, after the update, even if the checkbox remains unchecked, the hidden field still produces an error when attempting to save the content.
The issue seems to be related to the handling of field dependencies and required status during the Drupal 9 to Drupal 10 upgrade. A proposed resolution is to review the changes in Drupal 10 that might affect the visibility and required status of dependent fields. This could involve investigating changes in the field API and/or form rendering logic. Once identified, a patch or workaround can be developed to ensure that the required field behaves as expected based on the control field's value.
N/A. The focus is on addressing the backend logic to ensure proper visibility and required status handling for dependent fields.
Depending on the findings during the investigation, there might be necessary changes or enhancements to support the correct handling of field dependencies and required status in Drupal 10.
No changes to the data model are expected as part of this issue.
Active
4.0
Code
I am also facing the same issue.
If you get any solution let me knpow.
Thanks
is it related to this https://www.drupal.org/project/conditional_fields/issues/3344587 📌 Support field turning hidden by condition to loose its required status Needs work