Breaking: Site sets and static templates have been restructured 

Description 

The TypoScript and the page TSconfig of this extension were shipped twice: the static template read Configuration/TypoScript/, and the site set fgtclb/academic-programs shipped its own constants.typoscript and setup.typoscript, each of them a single @import of that folder. The page TSconfig existed only as the wizard file Configuration/TSconfig/page.tsconfig, pulled in by a glob in Configuration/page.tsconfig, and was not selectable on a page at all.

Both mechanisms now read one physical copy of every file, and both of them deliver the extension per component instead of as one block:

• Configuration/TypoScript/ keeps the shared plugin.tx_academicprograms block and the page object of the page type. Both content elements are driven by the one plugin, so that block is shipped once and every component folder names it in a one-line include_static_file.txt.
• Configuration/TypoScript/ProgramList/ and Configuration/TypoScript/ProgramDetails/ are the two component folders — what the static template registers and what the matching set points its typoscript key at.
• Configuration/TSconfig/<Component>/page.tsconfig holds the page TSconfig of a component and is what the page field Page TSconfig offers and what the set points its pagets key at.
• Configuration/TypoScript/Full/ and Configuration/TSconfig/Full/page.tsconfig are the aggregates for installations that do not use site sets.

The content elements are now hidden by default. The always-included Configuration/page.tsconfig removes both content element types from the selectable ones, and the page TSconfig of a component adds its own back — so an element is offered where it is wanted instead of on every page of every installation. The TCA registration itself did not move, so the frontend renders existing records exactly as before. Editing such a record in the backend is a different matter — read the warning below before upgrading.

The styles.content.getContent override that Configuration/TypoScript/setup.typoscript used to import unconditionally is a component of its own now, Configuration/TypoScript/ContentLoad/setup.typoscript. It redefines a global TypoScript object path for every page of a site, so it must be possible to take the content elements without it.

The page type Academic program (doktype 20) and its backend layout AcademicProgram stay installation-wide. They are values stored on pages records and are not, and must not be, part of any opt-in set. The file that defines the layout moved from Configuration/TSconfig/Page/BackendLayouts/ to Configuration/TSconfig/BackendLayouts/, where the sibling extensions of this family keep theirs; the identifier pagets__AcademicProgram a page record stores is unchanged.

Impact 

A sys_template record that selected the static template of this extension keeps its stored value and keeps working: the registered folder is unchanged, only its label is. What it no longer delivers is the styles.content.getContent override, which moved into a component of its own.

A site package that imported one of the moved files by path fails to resolve it. @import of a missing file is silent, so this shows up as missing configuration rather than as an error message.

Both content elements are no longer offered in the backend until the page TSconfig of their component is included, through the site set or through the page field Page TSconfig.

The set fgtclb/academic-programs keeps its name and keeps delivering everything, so a site configuration that depends on it needs no change.

The duplicated backend template registration is gone 

This extension registered its EXT:backend template override twice, under two different keys and pointing at the same directory: templates.typo3/cms-backend.1730990129 in Configuration/page.tsconfig and templates.typo3/cms-backend.academic-programs in Configuration/TSconfig/page.tsconfig, which the first file globbed in. BackendViewFactory does not deduplicate, so fgtclb/academic-programs:Resources/Private/Backend was appended twice to every backend template, layout and partial root path on every page render.

Only templates.typo3/cms-backend.academic-programs is left, in Configuration/page.tsconfig, which is what the sibling extensions of this family use. Nothing an integrator configures changes with it — but an own site package that overrode the numeric key templates.typo3/cms-backend.1730990129 has to be adjusted.

Affected Installations 

Installations that import one of the shipped files from an own site package, that use one of the content elements of this extension without including its page TSconfig, or that relied on the styles.content.getContent override arriving with the plugin configuration.

Migration 

Adjust every @import in an own site package:

The entry in the sys_template record keeps its value and changes its label:

Add the page TSconfig entry, which did not exist before, in the page record of the site root, tab Resources, field Page TSconfig: Academic Programs: All components (academic_programs), stored as EXT:academic_programs/Configuration/TSconfig/Full/page.tsconfig. Without it the content elements are not selectable any more, and existing records of them lose their CType when they are saved from the backend form.

Sites that use the site set instead need no migration — but they must not use both mechanisms at once, see the Configuration chapter.

A site configuration may name the new component sets instead of the aggregate: