Breaking: Site sets and static templates have been restructured 

Description 

This extension already shipped both delivery mechanisms, and it already hid its content element by default — it is the only academic extension that did. What it shipped them through were four one-line @import files around two real ones:

• Configuration/TypoScript/Default/setup.typoscript and Configuration/Sets/AcademicStudyPlan/setup.typoscript both imported Configuration/TypoScript/Includes/ContentElement.typoscript.
• Configuration/TSconfig/Default.tsconfig and Configuration/Sets/AcademicStudyPlan/page.tsconfig both imported Configuration/TSconfig/Includes/academic-study-plan.tsconfig.

The indirection is gone. Both mechanisms now read one physical copy of every file, and both of them deliver the extension per component:

• Configuration/TypoScript/ContentElement/ holds the TypoScript of the Academic Study Plan content element and is what the static template registers and what the set points its typoscript key at.
• Configuration/TSconfig/ContentElement/page.tsconfig holds its page TSconfig 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.

Three things changed beyond the paths:

• The three Fluid root paths of the content element are constants now, plugin.tx_academicstudyplan.view.templateRootPath , …partialRootPath and …layoutRootPath . They were assigned in the setup directly and could only be changed by overriding the content element object. The shipped values are unchanged, and the new constants.typoscript is delivered by both mechanisms together with the setup.
• The wizard entry of the content element is registered unconditionally. It used to sit in a [typo3.branch == "12.4"] condition, which never matched on a version this release supports.
• The published set fgtclb/academic-study-plan-default is an alias without payload now. It depends on the new aggregate fgtclb/academic-study-plan , which depends on the component set fgtclb/academic-study-plan-content-element .

Impact 

A sys_template record that selected the old static template keeps its stored value, and that value now points at a folder holding no constants.typoscript and no setup.typoscript. It is not an error — the frontend simply loses the content element configuration, and the element renders as an empty content element.

A page record that selected the old page TSconfig file keeps its stored value too, and that value now points at a file that does not exist. An unresolved page TSconfig include is silent, so the content element stops being selectable on that page tree without any message.

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

Affected Installations 

Installations that select the static template or the page TSconfig file of this extension, that depend on its site set, or that import one of the shipped files from an own site package.

Migration 

Replace the static template entry in the sys_template record:

Replace the page TSconfig entry in the page record of the site root, tab Resources, field Page TSconfig:

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

Adjust every @import in an own site package:

A site configuration may name the new sets instead of the published one: