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 for what happens otherwise.

Note

Site sets arrived in TYPO3 v13.1. On TYPO3 v12 the set files this extension ships are never read, and the static templates plus the page TSconfig files below are the only way to configure a site.

What the sets contain

This extension ships three content elements, so it ships three component sets and one aggregate set that depends on all of them.

All three are driven by one Extbase plugin, so they share one TypoScript block, plugin.tx_academicjobs. That block is shipped once, in Configuration/TypoScript/, and every component includes it. Which component sets a site names therefore decides which content elements the backend offers, not how much TypoScript is loaded.

Set	Delivers
`fgtclb/academic-jobs-new-job-form`	The Jobs New content element, the frontend form a job offer is entered with.
`fgtclb/academic-jobs-list`	The Jobs List content element.
`fgtclb/academic-jobs-detail`	The Jobs Detail content element.
`fgtclb/academic-jobs`	Everything above. This is the set to use unless you deliberately want a subset, and it is the name this extension published before the sets were cut per component — a site configuration that depends on it needs no change.

Every component set depends 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 site settings of this extension — the storage, detail, list and redirect pages, the notification e-mail, the job avatar upload and the content element header switch — are declared with the aggregate set. A site that depends on a single component set still gets the shipped defaults, but can only override them in Site Settings when it depends on fgtclb/academic-jobs.

The content elements are hidden by default

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

Warning

This changed in version 2.4. Before it, all three elements were selectable on every page of every installation. Read Breaking: Site sets and static templates have been restructured before upgrading. An existing content element on a page that does not enable its component keeps its type: the backend shows the stored type followed by (not enabled on this page), and saving keeps it. Content elements whose type an earlier save already replaced are not repaired, the record history shows their former type.

Include the site set

Add the set to the config.yaml of the site that should offer the content elements:

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

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

Include static templates

For an installation that still configures its frontend through sys_template records — and for every installation on TYPO3 v12 — 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

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

Entry	Delivers
Academic Jobs: Jobs New (academic_jobs)	The TypoScript of the Jobs New content element.
Academic Jobs: Jobs List (academic_jobs)	The TypoScript of the Jobs List content element.
Academic Jobs: Jobs Detail (academic_jobs)	The TypoScript of the Jobs Detail content element.
Academic Jobs: All components (academic_jobs)	Every component this extension ships, in one entry.
Academic Jobs: Shared plugin settings (academic_jobs)	The shared `plugin.tx_academicjobs` block on its own. This is the entry an installation stored before the configuration was cut per component, and it keeps working — but it does not make any content element selectable, which the page TSconfig below does.

Include static page TSconfig

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

Entry	Delivers
Academic Jobs: Jobs New (academic_jobs)	Makes the Jobs New content element selectable, and configures its entry in the new content element wizard.
Academic Jobs: Jobs List (academic_jobs)	The same for Jobs List.
Academic Jobs: Jobs Detail (academic_jobs)	The same for Jobs Detail.
Academic Jobs: All components (academic_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

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. For this extension that is the whole plugin.tx_academicjobs constants block: the Fluid root paths, the storage and target page ids, the notification e-mail, the job avatar upload settings and the content element header switch, among others.

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.

The question does not arise on TYPO3 v12 either, where there is only one mechanism.