---
title: "Validation settings"
manual: "Academic Jobs"
version: "2.4"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-jobs:configuration-validations@2.4"
source: "Configuration/Validations/Index.rst"
rendered: "2026-10-26T16:44:00+00:00"
---

# Validation settings {#configuration-validations}

`Configuration/AcademicJobs/Settings.yaml` describes which fields of a job
record are required, and how they are rendered in the public *new job* form.

> [!WARNING]
> **Attention**
>
> The syntax of this file is still considered experimental and may change in a
> future release. Read [Current limitations](https://docs.typo3.org/permalink/fgtclb/academic-jobs:configuration-validations-limits@2.4) before relying
> on it — not every keyword takes effect in every place.

## The file {#the-file}

The shipped configuration defines a single set, `job`. Its keys are
**property names** in camel case, each carrying a list of flags:

```yaml
validations:
  job:
    title:
      - required
    link:
      - url
    contactEmail:
      - email
    contactPhone:
      - tel
```

A property that is not listed is neither required nor specially rendered.

## Where the settings take effect {#where-the-settings-take-effect}

The configuration is read in three independent places, and — this is the
important part — **they do not all understand the same keywords**:

| Keyword | New job form | Server side validation | Backend (TCA) |
| --- | --- | --- | --- |
| `required` | Marks the field with an asterisk | Value must not be empty, `0` counts as empty for a number such as the job type | Not applied |
| `email` | Renders `<input type="email">` | Value must be an email address | Not applied |
| `url` | Renders `<input type="url">` | Value must be a URL | Not applied |
| `number` | Renders `<input type="number">` | **No validation** | Not applied |
| `tel` | Renders `<input type="tel">` | **No validation** | Not applied |

Server side validation runs when a job is **created** through the frontend form.
It does not run for records edited in the TYPO3 backend.

## Current limitations {#configuration-validations-limits}

> [!WARNING]
> `disabled` and `readonly` are **not supported** by this
> extension, even though older comments inside the shipped
> `Settings.yaml` mention them.
>
> They do not lock a field anywhere. Worse, because the form takes the first
> keyword that is not `required` and uses it directly as the HTML input
> type, writing `disabled` produces `<input type="disabled">`,
> which browsers fall back to rendering as an ordinary text field. Do not use
> these two keywords here.
>
> They *are* supported by **academic_persons**, which is a separate
> mechanism — see [its validation settings](https://docs.typo3.org/p/fgtclb/academic-persons/2.4/en-us/Configuration/Validations/Index.html).

Further points to be aware of:

-   **Keywords are case sensitive.** `Required` or `EMAIL` are
    silently ignored. Always write them in lower case.
-   **Any unknown keyword becomes an HTML input type** in the new job form, as
    described in the warning above. A typo therefore produces an invalid input
    type rather than being ignored.
-   `number` marks the field as numeric in the form but adds no server
    side validation, so a non-numeric value submitted by other means is
    accepted.
-   `required` on a field stored as a number, such as the job type and
    the employment type, refuses `0`. That is the value the
    **Please choose** option of their selects submits, so `0` cannot
    be a value an integrator offers for a required select.
-   `number` renders an input that accepts digits only. Do not use it
    for a phone number, which is written with a leading `+` and with spaces,
    use `tel` instead.
-   The configuration is **not** applied to the TYPO3 backend. Required fields
    in the backend record editor are configured separately in the extension's
    TCA, and the two may differ.

## Overriding the settings {#overriding-the-settings}

Settings are collected from **all installed extensions**. Every package that
contains `Configuration/AcademicJobs/Settings.yaml` contributes, and the
package loaded last wins.

To change them for an installation:

1.  Add `Configuration/AcademicJobs/Settings.yaml` to your site package.
1.  Make the site package **depend on** **academic_jobs** in its
    `composer.json` or `ext_emconf.php`, so that it is loaded after
    it.
1.  Repeat the **complete** `validations` block, see the warning below.
1.  Flush the TYPO3 caches — the parsed settings are cached, and a changed file
    has no effect until the cache is cleared.

> [!WARNING]
> The files are merged on the top level only. `validations` is a
> top-level key, so a site package that defines it replaces the whole block —
> anything it does not repeat is lost, not inherited.
>
> Copy the whole `validations` block from
> `EXT:academic_jobs/Configuration/AcademicJobs/Settings.yaml` and edit
> the copy. There is no syntax for removing a single flag from a single field.

There is no TypoScript and no site set equivalent for these settings.