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.

What the sets contain

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

Set	Delivers
`fgtclb/academic-study-plan-content-element`	The Academic Study Plan content element: its TypoScript (`tt_content.academic_study_plan`, the Fluid root paths and the data processor that assigns the semesters and modules to the template) and the page TSconfig that makes the content element selectable in the backend.
`fgtclb/academic-study-plan`	Everything above. This is the set to use unless you deliberately want a subset.
`fgtclb/academic-study-plan-default`	The name this extension published before the sets were cut per component. It delivers exactly what `fgtclb/academic-study-plan` delivers, and is kept so that existing site configurations keep working.

The 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 content element is hidden by default

EXT:academic_study_plan 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 Academic Study Plan selectable in the backend again — without one of them the content element is not offered, and existing records keep rendering.

This is not new in version 2.4: this extension always hid its content element. What changed is the file that brings it back and the name it is registered under — see Breaking: Site sets and static templates have been restructured.

Include the site set

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

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

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

Include static templates

For an installation that still configures its frontend through sys_template records, the same files are registered as static templates and as selectable page TSconfig files.

Tip

On TYPO3 v13 and v14 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 Study Plan: Content element (academic_study_plan)	The TypoScript of the Academic Study Plan content element.
Academic Study Plan: All components (academic_study_plan)	Every component this extension ships, in one entry.

Include static page TSconfig

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

Entry	Delivers
Academic Study Plan: Content element (academic_study_plan)	Makes the Academic Study Plan content element selectable, and configures its entry in the new content element wizard.
Academic Study Plan: All components (academic_study_plan)	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 those are the three Fluid root paths of the content element.

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.