---
title: "Important: The page TSconfig directory is now spelled TSconfig"
manual: "Academic StudyPlan"
version: "main"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-study-plan:important-1787141400@main"
source: "Changelog/2.4/Important-PageTsConfigDirectoryRenamed.rst"
rendered: "2026-10-17T08:48:10+00:00"
---

# Important: The page TSconfig directory is now spelled `TSconfig` {#important-1787141400}

## Description {#description}

The extensions of this set spelled their page TSconfig directory in three
different ways: `TsConfig`, `TSconfig` and `TSConfig`. They
now all use `TSconfig`, which is how TYPO3 spells the term and what the
core documentation uses.

In this extension the directory was `Configuration/TsConfig`.

Nothing was broken before, because every import matched the directory it pointed
at. The reason to change it is that a filesystem is case sensitive on Linux and
case insensitive on macOS and Windows, so a path copied between two of these
extensions resolved on one machine and silently not on another. A page TSconfig
`@import` that does not resolve raises no error, the configuration
is simply absent.

This extension additionally registers a selectable static page TSconfig include,
through `ExtensionManagementUtility::registerPageTSConfigFile()`. The
registration was updated with the directory and reorganised in the same release,
which changed both its label and the value a page record stores.

> [!WARNING]
> That value is not code, it is **data**: an integrator selected it in the
> page field **Page TSconfig**, and TYPO3 stored the path in
> `pages.tsconfig_includes`. The stored path is not rewritten by an
> update, it simply stops resolving. An unresolved page TSconfig include
> raises nothing at all, so the content element quietly stops being selectable
> on that page tree. Every page record that selected **Academic
> StudyPlan (Default) (academic_study_plan)** has to be edited once. See
> [Breaking: Site sets and static templates have been restructured](https://docs.typo3.org/permalink/fgtclb/academic-study-plan:breaking-site-sets-and-static-templates-restructured@main) for what to
> select instead.

## Impact {#impact}

Every file this extension ships moved with the directory. The imports inside
the extension were updated in the same change, so an installation that only
installs the extension has nothing to do.

**An integrator who references these paths from their own configuration has to
update them**, because the old path no longer exists. The files below the
directory were reorganised in the same release, so the new path is not the old
one with the spelling corrected. Take it from the table in
[Breaking: Site sets and static templates have been restructured](https://docs.typo3.org/permalink/fgtclb/academic-study-plan:breaking-site-sets-and-static-templates-restructured@main):

**Page TSconfig of your own site package**

```typoscript
# before
@import 'EXT:academic_study_plan/Configuration/TsConfig/Default.tsconfig'
# after
@import 'EXT:academic_study_plan/Configuration/TSconfig/ContentElement/page.tsconfig'

# before
@import 'EXT:academic_study_plan/Configuration/TsConfig/Includes/academic-study-plan.tsconfig'
# after
@import 'EXT:academic_study_plan/Configuration/TSconfig/ContentElement/page.tsconfig'
```

## Affected Installations {#affected-installations}

Every installation that imports a page TSconfig file of this extension by path,
or that copied such a path into its own site package. An installation that
relies only on the auto-included [`Configuration/page.tsconfig`](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FileStructure/Configuration/PageTsconfig.html#file-extension-configuration-page-tsconfig) of the
extension, or on its site set, is unaffected.