Important: The job validation flags follow the persons vocabulary
Description
The flags of Configuration/ are read by the
shared settings classes of academic_base, and mean what they mean
in academic_persons:
- Flags are read regardless of case and of spaces around them. A flag
written
Requiredmade nothing required before and rendered<input type="Required">. It makes the field required now. - A flag outside the shared vocabulary is ignored. Before, the new job form
rendered the first flag that was not
requiredas the HTML input type, so a typo produced an input such as<input type="disabledd">. readonly,disabledandfrontendreadonlytake effect. They cancelrequiredin the form and in the check of a submitted job, and the first two lock the field in the backend. The form keeps offering the field.telrenders a telephone input.
The shipped settings mark the contact phone with
tel
instead of
number
. The form renders
<input type="tel">
for it, so a
browser accepts a number like +49 30 123, which a number input
refused. A site package that copied the whole block of 2.x still names
number
and has to change it, see
Breaking: The job validation settings reach the backend.
A required settings field the job has no property for is left out of the check of a submitted job. Before, it made every submission fail.
Affected installations
Every installation that renders the new job form: the contact phone input changes its type. Installations whose site package ships its own settings file with flags in other than lower case, with an unknown flag, or with a field the job has no property for.