Configuration 

This extension ships no frontend TypoScript. What it does ship is the backend page TSconfig that labels the content element group Academic, the group every academic extension sorts its content elements into.

That page TSconfig is delivered in three ways, and the first one needs no configuration at all:

  • Configuration/page.tsconfig of this extension, which TYPO3 includes for the whole installation. The group is therefore labelled on every installation, whatever the site configuration says.
  • The site set fgtclb/academic-base-ctype-group , for a site configuration that lists it — usually because another academic extension depends on it.
  • The page TSconfig file registered for the page field Page TSconfig.

All three read the same file, so nothing changes when more than one of them applies.

What the sets contain 

Set Delivers
fgtclb/academic-base-ctype-group The label of the content element group Academic in the new content element wizard.
fgtclb/academic-base Everything above. This is the set to use unless you deliberately want a subset.

Every academic extension that ships content elements depends on fgtclb/academic-base-ctype-group, so a site that includes one of those sets gets this one with it and needs no entry of its own.

No content element is hidden by default 

This extension ships no content element of its own, so it hides none. The content elements of the other academic extensions are hidden for the whole installation and brought back per component by the extension that ships them — see the Configuration chapter of that extension.

An existing content element keeps its hidden type 

A content element that already exists keeps its content type on a page where that type is not enabled — a site that does not include the component, or a page that restricts the content types with its own page TSconfig. The Type field shows the stored type as the selected option, followed by (not enabled on this page), so saving the record leaves the type as it is.

Choosing another type and saving changes it as usual; the hidden type is not offered again afterwards. A new content element is only offered the types enabled on its page.

This covers every content element in the Academic group, without any configuration. Content types of other extensions keep the behaviour of TYPO3, which selects the first available option instead. See Important: A hidden academic content type stays selected.

Include the site set 

On TYPO3 v13, add the set to the config.yaml of the site:

config/sites/my-site/config.yaml (diff)
 base: 'https://example.com/'
 rootPageId: 1
+dependencies:
+  - fgtclb/academic-base
Copied!

See also TYPO3 Explained, Using a site set as dependency in a site.

Include static templates 

For an installation that configures itself through records rather than through a site configuration — which on TYPO3 v12 is every installation — the same file is registered as a selectable page TSconfig file.

Include static TypoScript 

This extension ships no TypoScript and therefore registers no static template.

Include static page TSconfig 

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

Entry Delivers
Academic Base: Content element group (academic_base) The label of the content element group Academic.
Academic Base: All components (academic_base) 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 

For this extension both mechanisms assign the same two values, so combining them is harmless. For the academic extensions that also ship TypoScript it is not — see the Configuration chapter of the extension in question. Use one mechanism per site.