---
title: "Important: The static template and the backend layout are registered correctly"
manual: "Academic Partners"
version: "main"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-partners:important-1786968600@main"
source: "Changelog/2.4/Important-StaticTemplateAndBackendLayoutRegistration.rst"
rendered: "2026-10-26T19:20:19+00:00"
---

# Important: The static template and the backend layout are registered correctly {#important-1786968600}

## Description {#description}

Two registrations of this extension did not reach an installation.

**The static template was registered under the wrong extension key.**
[`Configuration/TCA/Overrides/sys_template.php`](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FileStructure/Configuration/TCA/Index.html#file-extension-configuration-tca-overridessomefile-php) passed
`'academic_programs'` to
`ExtensionManagementUtility::addStaticFile()`, so the entry offered in a
template record up to version 2.3, **Academic Partners Page Setup**,
pointed at `EXT:academic_programs/Configuration/TypoScript/`, the
TypoScript of a different extension. The TypoScript of this extension was
registered nowhere and could only be reached through the site set
`fgtclb/academic-partners`.

What that cost an installation without site sets: the page template directory
of this extension never entered `page.10.templateRootPaths`, and
the `PartnershipProcessor` data processor was never registered, so
partnerships were not resolved on any page. An installation that has this
extension without [`fgtclb/academic-programs`](https://packagist.org/packages/fgtclb/academic-programs) included nothing at all,
silently, because `SysTemplateTreeBuilder` skips an include whose
extension is not loaded.

**The backend layout was imported by the site set only.**
[`Configuration/page.tsconfig`](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FileStructure/Configuration/PageTsconfig.html#file-extension-configuration-page-tsconfig) is included for the whole installation
since TYPO3 v12.0 (Feature: #96614), while a site set is opt-in per site. The
backend layout of the page type this extension registers was imported only by
[`Configuration/Sets/AcademicPartners/page.tsconfig`](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FileStructure/Configuration/Sets/Index.html#file-set-page-tsconfig). On a site that does
not enable that set the layout `pagets__AcademicPartner` resolved
nowhere: the page properties showed **\[ MISSING LABEL \]** for it and it
could not be selected for a new page at all. On TYPO3 v12 there was no delivery
path for the layout whatsoever, because site sets arrived in TYPO3 v13.1
(Feature: #103437).

The static templates of this extension are registered under its own key now,
and [`Configuration/page.tsconfig`](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FileStructure/Configuration/PageTsconfig.html#file-extension-configuration-page-tsconfig) imports the backend layout. The missing
label of the layout's content column was added to
`Resources/Private/Language/locallang_be.xlf`. The empty
`Configuration/TsConfig/page.tsconfig` was removed.

## Impact {#impact}

The static templates of this extension include its own TypoScript. The backend
layout is available on every installation, whether or not it uses site sets.

The static templates were also cut per component in this version, and the
entry **Academic Partners Page Setup** is now called
**Academic Partners: Shared plugin settings and page rendering**, see
[Breaking: Site sets and static templates have been restructured](https://docs.typo3.org/permalink/fgtclb/academic-partners:breaking-site-sets-and-static-templates-restructured@main).

## Affected Installations {#affected-installations}

All installations of this extension.

## Migration {#migration}

The static template fix is **not self-healing**. A template record that
selected the entry before stores
`EXT:academic_programs/Configuration/TypoScript/`, which is still a valid
registration of the other extension, so the record keeps working and keeps
including the TypoScript of [`fgtclb/academic-programs`](https://packagist.org/packages/fgtclb/academic-programs) instead of
this one.

Open the template record, tab **Advanced Options**, field
**Include TypoScript sets**, and add
**Academic Partners: All components (academic_partners)**, or the
component entries the site needs. Remove the selected
**Academic Programs: Shared plugin settings and page rendering
(academic_programs)** unless the site uses that extension on purpose.

No upgrade wizard ships for it: the stored value cannot be told apart from an
intentional selection of the programs entry, and rewriting it would break an
installation that meant the latter.

Nothing has to be done for the backend layout. Pages already carrying
`pagets__AcademicPartner` resolve it from now on.