---
title: "Feature: \"academic:upgrade:check\" finds stale configuration"
manual: "Academic Base"
version: "main"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-base:feature-upgrade-configuration-check@main"
source: "Changelog/3.0/Feature-UpgradeConfigurationCheck.rst"
rendered: "2026-10-17T08:47:46+00:00"
---

# Feature: "academic:upgrade:check" finds stale configuration {#feature-upgrade-configuration-check}

## Description {#description}

The console command `academic:upgrade:check` of `EXT:academic_base`
gained a second group of checks. It reads the stored configuration of the
installation and reports what no longer reaches the academic extensions, or
what reaches them twice. The group takes no argument and runs on every
invocation of the command:

```bash
vendor/bin/typo3 academic:upgrade:check
```

```text
Configuration

  ! static-template          sys_template:1
    The TypoScript record "Main" on page 1 includes the static template
    "EXT:academic_persons/Configuration/TypoScript/AcademicPersonsDefault", which holds no
    TypoScript in the installed version: TYPO3 skips it without a message. Select the static
    template of the installed version instead, or remove the value.

  i alias-set                site:main
    The site "main" depends on "fgtclb/academic-persons-default", which is an alias without
    payload kept for site configurations written before 3.0. Depend on
    "fgtclb/academic-persons" instead, or on the component sets the site actually needs.

1 problem and 1 notice in the stored configuration.
```

Six findings are reported:

| Finding | Meaning | Severity |
| --- | --- | --- |
| `static-template` | A TypoScript record includes a static template of an academic extension that the installation does not have, or whose folder holds no TypoScript in the installed version. | warning |
| `tsconfig-import` | A page, or a site's `page.tsconfig`, imports or selects a page TSconfig file of an academic extension that is not there. | warning |
| `tsconfig-syntax` | A page TSconfig includes an academic file with the `<INCLUDE_TYPOSCRIPT:` syntax, which TYPO3 v14 no longer reads. | warning |
| `alias-set` | A site depends on `fgtclb/academic-persons-default` or `fgtclb/academic-study-plan-default`, the alias sets kept for site configurations written before 3.0. | notice |
| `set-and-static-template` | A site depends on a set of an academic extension while a TypoScript record on its root page includes a static template of the same extension. | warning |
| `xclass` | A class of an academic extension is replaced through `$GLOBALS['TYPO3_CONF_VARS']['SYS']['Objects']`. | error when the replaced class is `final` or no longer exists, notice when it is a domain model, warning otherwise |

Each of these fails silently in TYPO3: a static template folder without
TypoScript, an `@import` that matches no file and a selected page
TSconfig file that is gone are all skipped without a message.

The command exits with `1` when at least one warning or error was found
in either group, with `2` on invalid input, and with `0` otherwise
\- a notice alone does not fail a pipeline. It only reads: no record, file or
site configuration is changed.

## In the status report {#feature-upgrade-configuration-check-report}

With `EXT:reports` installed the same findings are shown in
**System > Reports > Status report** under **Academic Base**,
one entry per finding, and a single **Nothing stale** entry when there
is nothing to report. `EXT:reports` stays optional and is not a
requirement of `EXT:academic_base`.

## The extension key became optional {#feature-upgrade-configuration-check-argument}

`academic:upgrade:check` took an extension key as a required argument. It
is optional now, because the configuration group needs none:

```bash
# the configuration of the installation
vendor/bin/typo3 academic:upgrade:check

# the same, plus the template overrides of one extension
vendor/bin/typo3 academic:upgrade:check academic_persons \
    --override-path=EXT:my_site/Resources/Private/Extensions/AcademicPersons/
```

An extension key still has to be given together with `--override-path` or
`--site`, and those options still have to be given together with an
extension key. Every invocation that was valid before stays valid and keeps its
exit status, with the configuration findings added to its output.

## Impact {#impact}

Integrators get a report for the configuration an upgrade leaves behind.
Measured against the last released 2.x, `2.3.4`: the page TSconfig
folders were spelled `Configuration/TsConfig/`,
`Configuration/TSConfig/` and `Configuration/TSconfig/` depending on
the extension and were unified to the last of the three, and the set folders
`Sets/AcademicPersonsDefault/` and `Sets/AcademicBaseCTypeGroup/`
became `Sets/Default/` and `Sets/CTypeGroup/`. Both are part of the
2.4 restructuring that 3.0 inherited - see
`Breaking-SiteSetsAndStaticTemplatesRestructured.rst` in the 2.4 changelog
of `EXT:academic_persons` \- so an installation coming from 2.3.x meets all
of it at once, and every import written against those paths resolves to nothing
without TYPO3 saying so. The same holds for a static
template folder that a release stopped delivering, and for an XCLASS of a class
that 3.0 made `final`.

Nothing is rewritten. The records, files and site configurations belong to the
project, and which of them to correct is a decision the report leaves to the
integrator.