t3skin for TYPO3

t3skin has been gone since TYPO3 8.6, yet many installations still run versions that need it

From TYPO3 4.0 to 8.5, t3skin was the system extension for backend styling. It defined the icons, colors, spacing and the entire look and feel of the TYPO3 backend. With TYPO3 8.6, backend styling moved entirely into the backend system extension, and t3skin was removed from the core. Even so, t3skin regularly turns up in audits of existing installations, because it is still installed on old systems, and references to it cause errors when those systems are upgraded to current TYPO3 versions. If t3skin shows up in your extension list, the signal is clear: the installation is either outdated or was not fully cleaned up during an earlier upgrade.

The only use cases left are legacy installations

The only legitimate scenario for t3skin is a TYPO3 installation on a version up to 8.5, in practice usually 4.5, 6.2 or 7.6 LTS, that cannot be upgraded for technical or organizational reasons. In such installations, t3skin provides the backend design. Without it, the backend would be visually unusable: missing icons, broken layouts, unreadable forms.

A second scenario is the transition phase during a migration. When an agency migrates a TYPO3 v6 installation to v12, t3skin remains part of the core in the intermediate steps up to 7.6 and disappears with the update to 8.7 LTS. What can cause problems afterwards are custom backend customizations built on t3skin.

A third (anti-)scenario rests on a misunderstanding: in TYPO3 v7, t3skin was a mandatory system extension and already shipped the new backend design there. It could not bring back an old backend design, and from TYPO3 8.6 on, t3skin no longer exists at all.

Technically, t3skin was a CSS and icon package without business logic

t3skin was not an extension in the classic sense (no controller, no model, no repository). It consisted of CSS files, icon sprites, a few JavaScript snippets for the backend interface and an ext_tables.php that registered it as a backend skin. It was a system extension because it shipped with the core under typo3/sysext/. All of its logic was visual: colors, fonts, spacing, icons. The TYPO3 core rendered the backend modules; t3skin only determined how they looked.

This job moved into the core step by step: TYPO3 7.0 converted the t3skin CSS to Less, 8.1 moved the backend CSS into the “backend” system extension, and 8.6 removed t3skin. In parallel, v7 switched the icons to an SVG-based icon system (IconFactory), and the CSS was later migrated to SCSS.

Problems arise when references to t3skin survive an upgrade

The most common problem is a blank or broken backend after a TYPO3 upgrade. t3skin itself cannot even be installed in a v12 installation; if the error is related to t3skin, it comes from custom extensions or backend customizations that still load files from EXT:t3skin. The result: buttons without backgrounds, icons that fail to load, module navigation that cannot be clicked. The fix: remove these references and switch to what the core provides. If the backend is so broken that the Extension Manager cannot be reached, the extension causing it can be deactivated from the command line in a classic installation: typo3/sysext/core/bin/typo3 extension:deactivate <extension-key>. Composer installations no longer have this command since TYPO3 11.4; there, the extension is removed via Composer.

Second problem: orphaned CSS files. Even after the upgrade, CSS files can remain in fileadmin/ or typo3temp/ and stay in the browser cache. A full cache clear (browser cache, TYPO3 cache, CDN cache) is therefore needed after the upgrade.

Third issue: backend customizations built on t3skin. Some agencies wrote custom backend CSS in TYPO3 v6 that used t3skin classes as its foundation. Once t3skin is gone, these customizations break. The fix: migrate the custom backend CSS to the current core CSS classes.

t3skin has no upgrade path, so migrating means removing it

There is no update from t3skin to a current version, because the extension has no successor. Its successor is the TYPO3 core itself. Migration therefore means: remove every reference to t3skin CSS classes in custom backend modules and use the IconFactory for custom icons. t3skin itself disappears with the core update; there is no need to uninstall it. Gosign carries out this cleanup as part of every TYPO3 migration and checks at the same time whether other legacy extensions (css_styled_content, rtehtmlarea, adodb) have remained in the installation and need to be removed as well.