---
title: "Deprecation: The static template path of version 2.3"
manual: "Academic StudyPlan"
version: "main"
source: "Changelog/2.4/Deprecation-LegacyStaticTemplatePath.rst"
rendered: "2026-10-02T15:38:26+00:00"
---

# Deprecation: The static template path of version 2.3 {#deprecation-legacy-static-template-path}

## Description {#description}

Up to version 2.3 this extension offered one static template, stored in a
`sys_template` record as
`EXT:academic_study_plan/Configuration/TypoScript/Default`. Version 2.4 moves
the TypoScript into component folders, see
[Breaking: Site sets and static templates have been restructured](Breaking-SiteSetsAndStaticTemplatesRestructured.html#breaking-site-sets-and-static-templates-restructured), and leaves no
TypoScript of its own in the folder of that path.

The path keeps delivering. Its `constants.typoscript` and
`setup.typoscript` import the files of the same name in
`Configuration/TypoScript/ContentElement/`, so a record that stores the
path gets what **Academic Study Plan: All components
(academic_study_plan)** delivers, and an import of the two files gets what an
import of the files in `Configuration/TypoScript/ContentElement/` gets.

In version 2.3 the folder also added the stylesheet and the script of the
content element to every page. The content element template registers them
itself now, switchable with
`plugin.tx_academicstudyplan.assets.css` and
`plugin.tx_academicstudyplan.assets.js`, so the path does not add
them to the page.

The path is offered in the static template list again, as **Academic
Study Plan: Path up to 2.3 (deprecated, use All components)
(academic_study_plan)**, so saving the record keeps it. It is deprecated and
will be removed in version 4.0.

> [!IMPORTANT]
> Version 2.3 had no `constants.typoscript` in this folder, and its
> `setup.typoscript` needed none. The setup reads constants now. A site
> package that imports only
> `EXT:academic_study_plan/Configuration/TypoScript/Default/setup.typoscript`
> has to import
> `EXT:academic_study_plan/Configuration/TypoScript/Default/constants.typoscript`
> into its constants as well — otherwise the template paths stay unresolved,
> and the content element cannot find its template.

## Impact {#impact}

An installation that selects **All components** or depends on the site
set notices nothing. An installation that still stores the path of version 2.3,
or imports its files, keeps its content element configuration.

A site that depends on the site set and still stores the path of version 2.3 in
its `sys_template` record, or imports its files, reads the TypoScript
twice, as it did in version 2.3. See [Do not combine both](../../Configuration/Index.html#one-mechanism-per-site) for what
that costs. From version 3.0 on, the command `academic:upgrade:check`
reports a site that combines the site set with a static template of the same
extension.

## Affected Installations {#affected-installations}

Installations that store
`EXT:academic_study_plan/Configuration/TypoScript/Default` in a
`sys_template` record, or import
`EXT:academic_study_plan/Configuration/TypoScript/Default/setup.typoscript`
in a site package.

## Migration {#migration}

Select **Academic Study Plan: All components (academic_study_plan)** in
the `sys_template` record instead of the path up to 2.3, or depend on the
set `fgtclb/academic-study-plan` in the site configuration.

Replace an import of the old files with the files in
`EXT:academic_study_plan/Configuration/TypoScript/ContentElement/`, or remove
it when the site depends on the site set.