This is the respective issue for https://www.drupal.org/project/drupal/issues/742344, a blocker for the #5346 backport, and related to #1040.
Problem/Motivation
Accessibility guidelines recommend specific, meaningful error messages when required form elements are empty. However, FAPI currently does not support custom error messages for required elements.
Proposed resolution
Support a
#required_errorproperty for form elements. If set, this message will be used when a required form element is empty, instead of the default "Field x is required." Additionally set a#required_but_emptyflag automatically during validation when the required field is empty. This is an internal property and is not set manually. It allows#element_validatehandlers to set a custom required error message, but without having to re-implement the complex logic to figure out whether the field value is empty.Remaining tasks
Commit feature and document these properties. The feature is a small API improvement that is applicable to both D8 and D7.
User interface changes
None.
API changes
Minor, backwards-compatible addition only. No existing code will be affected. Addition of two FAPI element properties:
#required_error#required_but_empty
Advocate for this issue: @klonos
Recent comments
Thanks for the response, Herb! Since I posted that I did some more testing and have posted this issue https://github.com/backdrop-contrib/tfa_basic/issues/33 In fact, if both email...
TFA - how to setup fallback options 'per user'
I'll test this tomorrow to see if I can replicate the problem and report back. It's not "per user" so it should be working.
TFA - how to setup fallback options 'per user'
As I work through things I flush the caches after every change I make. As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
custom module not showing up in modules list