--- title: "Breaking: Site sets and static templates have been restructured" manual: "Academic Contacts for Pages" version: "main" source: "Changelog/2.4/Breaking-SiteSetsAndStaticTemplatesRestructured.rst" rendered: "2026-09-18T06:17:05+00:00" --- # Breaking: Site sets and static templates have been restructured {#breaking-site-sets-and-static-templates-have-been-restructured} ## Description {#description} The TypoScript of this extension was shipped through a chain of `@import` statements: the static template read `Configuration/TypoScript/`, whose `setup.typoscript` imported `Configuration/TypoScript/Page/`, and the site set `fgtclb/academic-contacts4pages` shipped a `setup.typoscript` of its own that imported the first one again. The page TSconfig existed only as `Configuration/TSconfig/page.tsconfig`, reachable through the auto-included `Configuration/page.tsconfig` and through nothing else — it 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/List/` holds the TypoScript of the **Contact list** content element and is what the static template registers *and* what the set points its `typoscript` key at. Its `setup.typoscript` carries what `Configuration/TypoScript/Page/Plugin.typoscript` and `Configuration/TypoScript/Page/Fluidtemplate.typoscript` used to carry, with one difference: the three Fluid root paths were literals there and are constants now, declared in the `constants.typoscript` beside it. - `Configuration/TSconfig/List/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. The extension ships a `constants.typoscript` for the first time. It declares the three Fluid root paths of the plugin — `plugin.tx_academiccontacts4pages.view.templateRootPath`, `…partialRootPath` and `…layoutRootPath` — with exactly the values that were hard coded in the setup before, so a site that changes nothing renders exactly as it did. What is new is that these paths can now be overridden as constants, in the constant editor or in `config/sites//constants.typoscript`. The content element is now **hidden by default**. The always-included `Configuration/page.tsconfig` removes `academiccontacts4pages_list` from the selectable content element types, and the page TSconfig of the component adds it back — so the 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. ## Impact {#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 plugin configuration and the data processor that assigns the contacts of a page to the page template, and the plugin renders with no template paths. 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. The **Contact list** content element is no longer offered in the backend until the page TSconfig of the component is included, through the site set or through the page field **Page TSconfig**. > [!WARNING] > Do not open an existing **Contact list** record 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. The set `fgtclb/academic-contacts4pages` keeps its name and keeps delivering everything, so a site configuration that depends on it needs no change. ## Affected Installations {#affected-installations} Installations that select the static template of this extension in a `sys_template` record, that import one of the shipped files from an own site package, or that use the content element without including the page TSconfig of this extension. ## Migration {#migration} Replace the static template entry in the `sys_template` record: | Old entry | New entry | | --- | --- | | **Contacts for Pages (academic_contacts4pages)**, stored as `EXT:academic_contacts4pages/Configuration/TypoScript/` | **Academic Contacts4Pages: All components (academic_contacts4pages)**, stored as `EXT:academic_contacts4pages/Configuration/TypoScript/Full` — or **Academic Contacts4Pages: Contact list (academic_contacts4pages)**, stored as `EXT:academic_contacts4pages/Configuration/TypoScript/List` | Add the page TSconfig entry, which did not exist before, in the page record of the site root, tab **Resources**, field **Page TSconfig**: **Academic Contacts4Pages: All components (academic_contacts4pages)**, stored as `EXT:academic_contacts4pages/Configuration/TSconfig/Full/page.tsconfig`. Without it the content element is not selectable any more, and existing records of it 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. Adjust every `@import` in an own site package: | Old path | New path | | --- | --- | | `EXT:academic_contacts4pages/Configuration/TypoScript/setup.typoscript` | `EXT:academic_contacts4pages/Configuration/TypoScript/List/setup.typoscript` | | `EXT:academic_contacts4pages/Configuration/TypoScript/Page/Plugin.typoscript` | `EXT:academic_contacts4pages/Configuration/TypoScript/List/setup.typoscript` | | `EXT:academic_contacts4pages/Configuration/TypoScript/Page/Fluidtemplate.typoscript` | `EXT:academic_contacts4pages/Configuration/TypoScript/List/setup.typoscript` | | `EXT:academic_contacts4pages/Configuration/TypoScript/Page/` | `EXT:academic_contacts4pages/Configuration/TypoScript/List/setup.typoscript` | | `EXT:academic_contacts4pages/Configuration/TSconfig/page.tsconfig` | `EXT:academic_contacts4pages/Configuration/TSconfig/List/page.tsconfig` | > [!WARNING] > A site package that imports the setup must import the constants as well. > The three Fluid root paths are constants now, and TypoScript leaves an > undefined constant as its own literal text rather than reporting it — so a > site package that imports only > `…/Configuration/TypoScript/List/setup.typoscript` ends up with > `templateRootPaths.10` set to the string > `{$plugin.tx_academiccontacts4pages.view.templateRootPath}` and the plugin > fails with a missing template. > > ```typoscript > @import 'EXT:academic_contacts4pages/Configuration/TypoScript/List/constants.typoscript' > ``` > > Neither of the two shipped delivery mechanisms is affected: both read the > whole folder. A site configuration may name the new component set instead of the aggregate: | Set | Delivers | | --- | --- | | `fgtclb/academic-contacts4pages` | Unchanged in name, now delivers through the component set below. | | `fgtclb/academic-contacts4pages-list` | The **Contact list** content element only. |