Glossary: T

The Table Configuration Array (TCA) defines database tables and their backend form rendering in TYPO3. It controls fields, labels, render types, validation, relations, and how records appear and behave in the backend.

Use Cases for TCA

TCA is typically used to model data structures and editor forms, such as:

• Defining custom tables and fields for extensions
• Extending existing core tables (e.g. tt_content) with additional columns
• Configuring field render types, validations, and select options
• Setting up inline relations (IRRE) and many-to-many references

How TCA Works

• TCA is declared in PHP files under Configuration/TCA/ and loaded during TYPO3 bootstrap.
• The backend form engine reads TCA to render forms, labels, palettes, and tabs.
• Overrides in Configuration/TCA/Overrides/ adapt core or third-party configurations without patching their files.

Advantages

• Single source of truth for data structure and backend UI
• Powerful form rendering with validations and custo

The TYPO3 Extension Repository (TER) is the central platform for publishing, discovering, and managing TYPO3 extensions. It provides a trusted place where developers share their work and integrators or agencies find ready-to-use solutions.

Use Cases for the TER

The TER is typically used for extension management, such as:

• Publishing custom extensions to make them available for the community
• Searching and downloading extensions directly from the TYPO3 backend
• Managing updates and versioning for installed extensions
• Finding official and community-driven solutions for common requirements

How the TER Works

• Developers register and publish their extensions to the TER with version information.
• TYPO3 connects to the TER via the Extension Manager or Composer.
• Administrators install and update extensions directly from the repository.

Advantages

• Central platform for all TYPO3 extensions
• Direct integration with the TYPO3 backend and Composer
• Transparent versioning and update history
• Community-driven quality assurance

Typical Use Case

An agency requires a SEO extension. Using the Extension Manager, they search the TER, install the desired extension directly, and manage future updates seamlessly through the repository.

TypoScript is the configuration language used in TYPO3 to control how content is structured and displayed in the frontend. It is not a traditional programming language but rather a declarative syntax that tells TYPO3 how to render content.

Use Cases for TypoScript

TypoScript is typically used to define:

• Which content elements appear on which pages
• Which templates and structures are applied
• Which paths, IDs, colors, or other constants should be used system-wide

Structure of TypoScript

TypoScript usually consists of two main sections:

• Constants: Global values such as paths, IDs, or color codes that can be defined and changed in one place.
• Setup: The section where the actual page structure and output logic are configured. For example, it defines which menus are shown or how specific content is rendered.

Advantages

• No programming skills required – purely configuration-based
• Well structured and easy to understand
• Changes take effect immediately after saving (and clearing the cache)
• Can be edited directly in the TYPO3 backend (Template module)

Typical Use Case

A common use of TypoScript is customizing or extending the output logic of a website – for example, creating a custom navigation, embedding additional data sources, or conditionally hiding content elements on specific pages.

The Typoscript Root Template is the root template of a TYPO3 page. This is usually the basic configuration and further configurations are integrated.