--- title: "Breaking: Site sets and static templates have been restructured" manual: "Academic Partners" version: "main" source: "Changelog/2.4/Breaking-SiteSetsAndStaticTemplatesRestructured.rst" modified: "2026-09-17T07:34:13+00:00" --- # 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-partners` 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/Wizards/NewContentElement.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_academicpartners` block and the `page` object of the page type. All four 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/List/`, `Configuration/TypoScript/Map/`, `Configuration/TypoScript/PartnershipsList/` and `Configuration/TypoScript/PartnershipsTeaser/` are the four component folders — what the static template registers *and* what the matching set points its `typoscript` key at. - `Configuration/TSconfig//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 all four 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 partner** (doktype 40) and its backend layout **AcademicPartner** are unchanged and stay installation-wide. They are values stored on `pages` records and are not, and must not be, part of any opt-in set. ## 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. The four 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**. > [!WARNING] > Do not open an existing record of one of these content elements in the > backend form on a page that does not include that page TSconfig. An item > removed through `TCEFORM.tt_content.CType.removeItems` is > excluded from the **\[ invalid value \]** fallback TYPO3 otherwise > adds for a stored value it does not know, and the stored value is dropped > from the form data as well. The field **Type** therefore comes up > with nothing selected, and **saving the record writes whatever the browser > preselected into** `CType` — the record silently becomes another > content element. The frontend keeps rendering it correctly until that > happens. > > Include the page TSconfig of the component on every page tree that holds > such records, and do it before editing them. > [!WARNING] > The Fluid template of the page type renders > `styles.content.getContent` through > ``, and > that ViewHelper throws when the path is undefined. A site that deliberately > opts out of `fgtclb/academic-partners-content-load` and still uses the page > type has to define `styles.content.getContent` itself. The set `fgtclb/academic-partners` keeps its name and keeps delivering everything, so a site configuration that depends on it needs no change. ## 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: | Old path | New path | | --- | --- | | `EXT:academic_partners/Configuration/TypoScript/constants.typoscript` | Unchanged. | | `EXT:academic_partners/Configuration/TypoScript/setup.typoscript` | Unchanged, but it no longer imports the `styles.content` override below. | | `EXT:academic_partners/Configuration/TypoScript/Content/ContentLoad.typoscript` | `EXT:academic_partners/Configuration/TypoScript/ContentLoad/setup.typoscript` | | `EXT:academic_partners/Configuration/TypoScript/Content/` | `EXT:academic_partners/Configuration/TypoScript/ContentLoad/` | | `EXT:academic_partners/Configuration/TSconfig/Wizards/NewContentElement.tsconfig` | `EXT:academic_partners/Configuration/TSconfig/Full/page.tsconfig` | | `EXT:academic_partners/Configuration/TSconfig/Wizards/*.tsconfig` | `EXT:academic_partners/Configuration/TSconfig/Full/page.tsconfig` | | `EXT:academic_partners/Configuration/Sets/AcademicPartners/constants.typoscript` | Removed. It was a one-line `@import` of the file above it in this table. | | `EXT:academic_partners/Configuration/Sets/AcademicPartners/setup.typoscript` | Removed, for the same reason. | The entry in the `sys_template` record keeps its value and changes its label: | Old entry | New entry | | --- | --- | | **Academic Partners Page Setup (academic_partners)**, stored as `EXT:academic_partners/Configuration/TypoScript/` | **Academic Partners: Shared plugin settings and page rendering (academic_partners)**, same stored value — or **Academic Partners: All components (academic_partners)**, stored as `EXT:academic_partners/Configuration/TypoScript/Full`, which also carries the content load override. | Add the page TSconfig entry, which did not exist before, in the page record of the site root, tab **Resources**, field **Page TSconfig**: **Academic Partners: All components (academic_partners)**, stored as `EXT:academic_partners/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: | Set | Delivers | | --- | --- | | `fgtclb/academic-partners` | Unchanged in name, now delivers through the component sets below. | | `fgtclb/academic-partners-list` | The **Partners List** content element only. | | `fgtclb/academic-partners-map` | The **Partners Map** content element only. | | `fgtclb/academic-partners-partnerships-list` | The **Partnerships List** content element only. | | `fgtclb/academic-partners-partnerships-teaser` | The **Partnerships Teaser** content element only. | | `fgtclb/academic-partners-content-load` | The `styles.content.getContent` override only. The aggregate depends on it; name the component sets above without it to opt out. |