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, as the only academic extension that did. What it shipped them through were four one-line @import files around three real ones:

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

The indirection is gone, apart from the deprecated path of version 2.3, see Deprecation: The static template path of version 2.3. 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: the content object, the Fluid root paths and the two frontend assets. It 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. On TYPO3 v12 that is every installation, because site sets do not exist there.

The directory holding the page TSconfig was renamed from Configuration/TsConfig to Configuration/TSconfig in the same release, and that directory is part of a value stored in page records, see Important: The page TSconfig directory is now spelled TSconfig.

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 new content element wizard entry moved out of the always-included Configuration/page.tsconfig into the page TSconfig of the component, together with the show key that TYPO3 v12 needs to offer the element in the wizard at all. Both arrive with the component now instead of with every installation. The [typo3.branch == "12.4"] condition around them is gone: the entry is registered on TYPO3 v13 as well now, where it changes nothing, because the wizard is built from TCA there and the entry carries the same key.
• 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. The folder of that value holds no TypoScript of its own any more. It imports the files of the component folder instead, so it delivers what All components delivers. The path is deprecated and will be removed in version 4.0, see Deprecation: The static template path of version 2.3.

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 Configuration/TypoScript/Default/setup.typoscript by path keeps getting the configuration, deprecated in the same way, once it also imports the constants.typoscript that folder holds now. Every other shipped file it imported by path fails to resolve. @import of a missing file is silent, so this 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 deprecated 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:

On TYPO3 v12 this is the only way to get the content element back. Site sets arrived in TYPO3 v13.1, and the set files of this extension are never read on v12.

Sites on TYPO3 v13 that use the site set instead need no migration. They must not use both mechanisms at once, see the Configuration chapter.

Adjust every @import in an own site package:

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