---
title: "Configuration"
manual: "Academic Bite Jobs"
version: "2.4"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-bite-jobs:configuration@2.4"
source: "Configuration/Index.rst"
rendered: "2026-10-26T16:43:50+00:00"
---

# Configuration {#configuration}

This extension ships its frontend TypoScript and its backend page TSconfig in
two forms: as TYPO3 **site sets**, and as classic **static templates** plus
**page TSconfig files** that are selected on a page. Both forms read the very
same files, so they configure an installation identically.

Pick one of them per site and stay with it — see
[Do not combine both](https://docs.typo3.org/permalink/fgtclb/academic-bite-jobs:one-mechanism-per-site@2.4) for what happens otherwise.

> [!NOTE]
> Site sets arrived in TYPO3 v13.1 (Feature: #103437). On TYPO3 v12 the sets
> below do nothing at all — the files they name are never read there — so an
> installation on that version configures itself through the static templates
> and the page TSconfig files described further down, and has to do so for the
> content element to be offered at all.

## What the sets contain {#configuration-components}

The extension ships one content element, so it ships one component set and one
aggregate set that depends on it.

| Set | Delivers |
| --- | --- |
| `fgtclb/academic-bite-jobs-list` | The **Job list** content element: its TypoScript (`plugin.tx_academicbitejobs`) and the page TSconfig that makes the content element selectable in the backend. |
| `fgtclb/academic-bite-jobs` | Everything above. This is the set to use unless you deliberately want a subset. |

Both depend on `fgtclb/academic-base-ctype-group`, the set of
**EXT:academic_base** that labels the content element group all academic
extensions sort their elements into.

## The content element is hidden by default {#configuration-hidden-by-default}

**EXT:academic_bite_jobs** hides its content element for the whole
installation and brings it back per component. Whichever of the two mechanisms
below you use, it is what makes **Job list** selectable in the backend
again — without one of them the content element is not offered, and existing
records keep rendering.

On TYPO3 v12 only the page TSconfig file is a candidate: the site set is not
read there. On that version the same file also carries the entry of the new
content element wizard, which v12 builds from page TSconfig rather than from
TCA (the TCA based wizard arrived in v13.0, Feature: #102834).

## Include the site set {#site-set}

On TYPO3 v13, add the set to the `config.yaml` of the site that should
offer the content element:

**config/sites/my-site/config.yaml (diff)**

```diff
 base: 'https://example.com/'
 rootPageId: 1
+dependencies:
+  - fgtclb/academic-bite-jobs
```

See also [TYPO3 Explained, Using a site set as dependency in a site](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/SiteHandling/SiteSets/Index.html#site-sets-usage).

## Include static templates {#static-templates}

For an installation that still configures its frontend through
`sys_template` records — which on TYPO3 v12 is every installation — the
same files are registered as static templates and as selectable page TSconfig
files.

> [!TIP]
> On TYPO3 v13 we recommend the site set — and if you use it, do not press
> the backend button **Create a root TypoScript record** on that
> site. The `sys_template` record it creates carries the flag
> **Clear** for constants and setup, and that flag discards everything
> the site sets contributed. An installation that is already in that state
> gets its configuration back by selecting the static templates below in that
> very record.

### Include static TypoScript {#static-typoscript}

Edit the `sys_template` record of the site root and add the entry to
**Include static (from extensions)**:

| Entry | Delivers |
| --- | --- |
| **Academic Bite Jobs: Job list (academic_bite_jobs)** | The TypoScript of the **Job list** content element. |
| **Academic Bite Jobs: All components (academic_bite_jobs)** | Every component this extension ships, in one entry. |
| **Academic Bite Jobs: Path up to 2.3 (deprecated, use All components) (academic_bite_jobs)** | The same as **All components**, for a record that still stores the path of version 2.3. Deprecated, removed in version 4.0, see [Deprecation: The static template path of version 2.3](https://docs.typo3.org/permalink/fgtclb/academic-bite-jobs:deprecation-legacy-static-template-path@2.4). |

### Include static page TSconfig {#static-pagetsconfig}

Edit the page record of the site root, tab **Resources**, field
**Page TSconfig**, and add the entry:

| Entry | Delivers |
| --- | --- |
| **Academic Bite Jobs: Job list (academic_bite_jobs)** | Makes the **Job list** content element selectable, and configures its entry in the new content element wizard. |
| **Academic Bite Jobs: All components (academic_bite_jobs)** | Every component this extension ships, in one entry. |

The setting is inherited by every page below the one it is set on.

## Do not combine both {#one-mechanism-per-site}

This can only happen on TYPO3 v13. A site that uses the site set **and** the
static template reads the shipped files twice. The site set is applied before the `sys_template` record, so
the second read happens after the site settings and after
`config/sites/<site>/constants.typoscript` — and it resets every constant
the extension ships a default for back to that default.

Nothing else is damaged: the **Constants** and **Setup** fields
of the `sys_template` record, the page TSconfig of a page and the page
TSconfig files selected on a page are all applied afterwards and still win. Use
one mechanism per site and the question does not arise.

-   [General configuration](https://docs.typo3.org/permalink/fgtclb/academic-bite-jobs:general-configuration@2.4)
-   [Labels](https://docs.typo3.org/permalink/fgtclb/academic-bite-jobs:labels@2.4)