Legacy installations: Directory structure¶
The structure below describes the directory structure in a legacy TYPO3 installation without Composer. For the structure in a Composer-based installation see Composer-based installations: Directory structure.
Files on project level¶
This folder contains the main entry script
index.php and might contain
publicly available files like a
robots.txt and files needed for the
server configuration like a
Directories in a typical project¶
This is a directory in which editors store files. It is used for the same files like public/fileadmin/ in the Composer-based directory structure.
Among others, this directory contains the two PHP files for accessing the TYPO3
typo3/index.php) and install tool (
It is a common practice in legacy installations to use symlinks to quickly
change between TYPO3 Core versions. In many installations you will find a symlink or folder
typo3_source that contains the folders typo3/,
and vendor/ and the file
index.php. In this case,
those directories and files only symlink to
typo3_source. This way
the Core can be updated quickly by changing the symlink.
Assuming your webroot is a directory called
public you could have
the following symlink structure:
typo3 -> typo3_src/typo3
typo3_src -> ../typo3_src-12.0.0
vendor -> typo3_src/vendor
index.php -> typo3_src/index.php
Amongst others, this directory contains the files
AdditionalConfiguration.php. See chapter
Configuration files for details.
This path can be retrieved from the Environment API, see getConfigPath().
Contains autoloading information. The files are updated each time an extension is installed via the Extension Manager.
Directory for third-party and custom TYPO3 extensions. Each subdirectory contains one extension. The name of each directory must be the extension key or the extension will not be loaded directly. You can put or symlink custom extensions and sitepackages here.
See extension files locations for more information on how the extensions are structured.
Directory for extension localizations. Contains all downloaded translation files.
This path can be retrieved from the Environment API, see getLabelsPath().
Directory for temporary files. It contains subdirectories (see below) for temporary files of extensions and TYPO3 components.
Although it is a most common understanding in the TYPO3 world that
typo3temp/ can be removed at any time, it is considered
bad practice to remove the whole folder. Developers should selectively
remove folders relevant to the changes made.
Directory for temporary files that should be publicly available (e.g. generated images).
Directory for temporary files that should not be accessed through the web (cache, log, etc).