This came up as an idea in https://github.com/backdrop/backdrop-issues/issues/5348#issuecomment-100...
@quicksketch
This issue ... may also be helpful if we were to ever add a server-side conditional system to replace
#states. By separating out the required message into its own property, we could conditionally display the required message without executing the entire form_validate()handler.
The #states property is a front-end only implementation. The lack of any server-side processing means any hidden fields cannot be required, or special validation handlers need to be added that validate field requireness manually.
Proposal
Introduce a new Form API property for designating conditional processing of parts of a form. This property would hide/show elements on the front end (like #states does already), but would also conditionally skip processing for hidden parts of the form. Hidden parts of the form would skip:
- Processing of the
#requiredattribute on hidden fields - Processing of
#element_validatehandlers on hidden fields - Remove any values from
$form_state['values']for hidden fields
Recent comments
I'll be very happy to test this and will report back.
Database update warning - but no pending updates
For anyone interested in an improvement to the Status report that should help with this, please see this issue and the associated pull request: https://github.com/backdrop/backdrop-issues/...
Database update warning - but no pending updates
@paucku I note from this issue here: https://github.com/backdrop-contrib/domain/issues/71 That you started getting this config formatting after changing the module to what Chat...
I need to understand how active and staging folders work โ configuration management