25+ Key Changes of TYPO3 v13.3

Welcome to my TYPO3 feature release series for TYPO3 version 13! In this blog, you'll discover in-depth insights into the key features, breaking changes, and deprecation introduced in TYPO3 v13.3. This release brings powerful improvements and exciting enhancements under the hood. Ready to dive into the latest innovations? Keep reading to stay informed and up to date!

Today, the TYPO3 community celebrated the release of TYPO3 v13.3, the fourth sprint feature update. This is an important step toward the Long-Term Support (LTS) version, expected in October 2024. These updates are designed to simplify workflows, improve user experience, and offer powerful tools for building and managing websites more efficiently. It comes with many strong features designed for

TYPO3 Integrators:
TYPO3 v13.3 introduces a new module at site management > settings configures static routes, new New HTTP header settings for Proxy/CDN, supports base64 image, upgrades to Fluid v4.0, and so on.

TYPO3 Editors:
For the editor, Launched helpful new dashboard widgets, moved elements by drag-n-drop to the page tree, changed the backend color scheme, etc.

TYPO3 Developers:
TYPO3 v13.3 comes with so many enhancements for the TYPO3 developers like Introduce Extbase file upload and deletion handling, Auto-created system TYPO3 TCA columns, Activating the shipped LintYaml executable for TYPO3, etc.

TYPO3 Administrators:
The TYPO3 Administrator got new features like Enable recycler by default, Change table restrictions UI to combine read and write permissions.

But before we get into the details, let's take a moment to appreciate all the tech and non-tech heroes who make TYPO3 great. This blog is a tribute to your hard work! #T3Kudos

Interested in the journey of TYPO3 v13 and how it evolved from the roadmap to versions 13.0 and 13.3? Don’t miss out—explore my detailed blog below for an inside look!

• Roadmap Announcement of TYPO3 v13
• What's New in TYPO3 v13.0?
• 15+ Key Highlights in TYPO3 v13.1
• 30+ Enhancements in TYPO3 v13.2

Before starting, look at the major goals of TYPO3 v13 LTS (long-term support).

In the past 8 weeks, TYPO3 Programmers have added over 20+ new features, making TYPO3 version 13.3 feature-complete.

With the feature freeze now in effect, it's time to dive into TYPO3 and explore its new capabilities before the LTS release. And, as always, get ready for the TYPO3 Release Party next month—fun is guaranteed!

Integrating Content Blocks into TYPO3 Core was a careful process to ensure stability and maintain existing options. Instead of adding it as a new system extension, TYPO3 chose to integrate its best features directly into the Core.

TYPO3 core selectively incorporated some of Content Blocks’ functionality into TYPO3 Core while keeping the extension available as an optional third-party tool. On the TYPO3 v13 LTS release day, both the Core and Content Types teams will launch Content Blocks version 1.0.0.

Looking ahead, TYPO3 v13 Long Term Support is just the start for Content Blocks. This release lays the groundwork for future innovations, with TYPO3 v14 on the horizon. TYPO3 is planning new features, including a user interface for creating content types. Stay tuned—there’s much more to come!

Note : IMHO, the cherry-pick strategy for EXT:content_blocks is a solid approach. However, it might be beneficial to include it in the TYPO3 core, similar to how other products and communities have made bold decisions (e.g., Gutenberg in WordPress). This would encourage people to take TYPO3 more seriously and build pages and content directly within the core. Hopefully, TYPO3 people will understand and start the project with content blocks for their next project.

Introduces a new Site Settings Editor that streamlines the management of per-site settings through the backend. This feature allows administrators to configure settings for each site via the config/sites/*/settings.yaml file.

Key Features:

• Centralized Management: Access and modify site-specific settings through the new backend module under Site Management > Settings.
• Persistent Settings: The editor updates only those settings that differ from the default values defined in the site’s configuration, ensuring minimal changes.
• Categorization: Settings can be organized into categories defined in settings.definitions.yaml, making it easier to manage and locate settings.

Usage Example:

In TYPO3 v13.3, you'll notice a refreshed look throughout the backend with updates to colors, TypoGraphy, icons, and spacing. These changes bring a modern and improved user experience to TYPO3. What are your thoughts? Share your feedback in the comments!

Introduces a convenient new feature that allows TYPO3 backend users to move content elements directly within the page tree. This enhancement simplifies content management by enabling users to drag and drop content elements from the “Page” module into the desired location on the page tree.

Key Features

• Drag-and-Drop Functionality: Easily move content elements from the “Page” module to any page in the page tree.
• Modal Window: After dropping, a modal window allows users to select the exact position for the content element and adjust the target page if needed.

Benefits

This new feature streamlines the process of reorganizing content across pages, making it faster and more intuitive to manage page layouts and content placement.

TYPO3 CMS now combines the management of read and write permissions into a single UI element for backend user groups. Previously separate fields for “Tables (listing)” and “Tables (modify)” have been merged. Users can now select permissions with options for “No Access,” “Read,” or “Read & Write,” and use convenient actions like “Check All” or “Toggle Selection.

The backend still processes permissions separately but presents them in a unified view, making permission management more intuitive.

Benefits

This update simplifies managing table permissions for backend user groups and enhances user experience with a streamlined interface. Custom integrations should be checked for compatibility with these changes.

TYPO3 version 13.3 brings exciting new dashboard widgets that enhance system management and oversight:

Overview

• Easily manage and view all internal notes (EXT:sys_note) directly from the TYPO3 backend.

Key Features

• Dedicated widgets for each internal note type.
• Requires access to the sys_note table and view permissions for relevant pages.

Benefits

• Streamline the tracking and management of internal notes, boosting visibility and efficiency.

Overview

• Quickly track and monitor the latest changes to pages within TYPO3.

Key Features

• Configurable page limit, defaulting to 10.
• History limit set to 1000 records.

Benefits

• Stay up-to-date with recent page modifications, enhancing content management and oversight.

These new widgets are designed to provide users with a more comprehensive view and better control over internal notes and page updates, making TYPO3’s backend more intuitive and efficient.

A new base64 attribute for the <f:image> and <f:uri.image> ViewHelpers, enhancing how images can be handled within your TYPO3 templates. This feature allows you to encode the image’s src attribute in base64, which can be particularly useful for including images in emails or reducing HTTP requests.

Key Features

• Base64 Encoding: The new base64="true" attribute encodes the image source as a base64 string.
• Enhanced Integration: Useful for embedding images directly within HTML, such as in FluidEmail templates, and minimizing HTTP requests.

Usage Example

To encode an image in base64, use the following code:

Benefits

This update simplifies embedding images directly into your content and improves performance by avoiding additional HTTP requests.

An exciting update to the <f:asset.css> and <f:asset.script> ViewHelpers by adding a new inline argument. This feature allows you to render asset files directly within your HTML as inline styles or scripts, which is particularly useful for improving the performance of content elements that appear at the top of your pages.

• Inline Rendering: The inline argument enables the content of CSS and JavaScript files to be embedded directly into the HTML <head> section.
• Performance Improvement: Useful for above-the-fold content, helping reduce Cumulative Layout Shift (CLS) and enhancing page load times.

Usage Example

TYPO3 v13.3 upgrades to Fluid 4.0, introducing improved support for boolean attributes in tag-based ViewHelpers. While older TYPO3 versions will continue using Fluid 2 with ongoing bug fixes, this update streamlines boolean attribute handling, making it easier and more intuitive.

Key Features

• Boolean Attribute Support: Fluid 4.0 now supports boolean attributes directly, similar to popular JavaScript frameworks.
• Variable and Casting Support: You can use variables and type casting with boolean attributes.

Usage Example

TYPO3 now offers an option to switch between color schemes in the backend. Users can select from automatic, light, or dark themes using new buttons in the user dropdown and a setting in User Settings.

Note: The dark color scheme is experimental and hidden behind the UserTS setting setup.fields.colorScheme.disabled until further notice.

Benefits

Admins can now easily switch between color schemes to customize their backend experience.

A new CLI command, typo3 upgrade:mark:undone, which allows you to mark a previously executed upgrade wizard as “undone” so it can be run again. This feature extends the functionality of the install tool to the command line interface.

Key Features

• Revert Wizards: Use the command to mark an upgrade wizard as undone.

Usage Example

typo3 upgrade:mark:undone <wizardIdentifier>

Important Notes

• Potential Data Inconsistencies: Running a wizard again might cause data inconsistencies.
• Prerequisite Issues: Wizards may not function correctly if their prerequisites have changed since the initial run.

Benefits

This new CLI command provides greater flexibility in managing upgrade wizards and is especially useful for administrators who need to rerun specific upgrade processes.

The lint:yaml command for the typo3 executable, designed to streamline and enhance the validation of YAML files before deployment. This feature helps prevent potential issues by allowing you to check YAML files for errors or inconsistencies.

Key Features

• Lint YAML Files: Easily validate YAML files with the new command:
• Get Help: Use the help argument to view usage options

Integrate this linting process into your quality assurance workflow to ensure that core, custom extension, and other YAML files are error-free before going live, all within the familiar typo3 command-line interface.

The ability to set up static routes for assets, allowing you to link directly to files typically found in directories like EXT:my_extension/Resources/Public/.

Key Features

• Static Routes for Assets: Define static routes for assets in your configuration:
• Site-Specific Configuration: Customize asset URLs on a per-site basis to deliver site-dependent resources, such as custom favicons or manifest files.

Usage Example

This new feature simplifies the management of static assets by integrating them directly into your site configuration, improving flexibility and ease of use for delivering custom assets.

A streamlined method for handling static route variables, eliminating the need for custom route aspect mappers to manage &cHash= signatures in URLs.

Key Features

• Direct Static Variable Declaration: Define static route variables directly in your route enhancer configuration without custom aspect mappers:
• Precedence and Requirements: Static route variables will only be applied if:
• No aspect mapper is configured (as aspect mappers take precedence).
• There is a corresponding requirements definition to restrict possible values and prevent cache issues.

Usage Example

Using the configuration above, a URL query parameter like 

&code=11f6ad8ec52a2984abaafd7c3b516503785c2072 would be translated

Benefits

This update simplifies route configuration by allowing direct declaration of static variables, making URL management more straightforward and reducing the need for complex custom implementations.

In TYPO3 v13.3, the core extension recycler is now enabled by default for all new installations.

Key Take Away

• Default Setting: Both new installations via Composer (TYPO3 CMS Base Distribution) and traditional tarball/zip downloads will have the recycler extension activated by default.
• Advantages: This change ensures that the recycler functionality, which helps manage and restore deleted records, is readily available for all fresh TYPO3 setups.

Benefits

This update simplifies the initial setup process by including the recycler extension by default, enhancing the system’s data management capabilities from the start.

TYPO3 v13.3 introduces the RedirectLoginErrorHandler, which allows you to configure custom redirects for 403 errors. This feature enables redirection to a login page when access is denied, and after successful login, users are redirected back to their original URL.

How It Works

Configure loginRedirectTarget to specify the login page and loginRedirectParameter to define the parameter used for passing the original URL. This handler supports parameters like return_url and redirect_url, which work with extensions such as EXT:felogin.

Note : Ensure your login extensions are set to handle these redirect modes. This new handler simplifies redirection compared to previous methods that required custom implementations.

TYPO3 v13.3 introduces a “close” button in the page module when a returnUrl argument is set. Clicking this button returns users to the previous module or a custom URL defined by returnUrl.

Usage Example

To display the button, backend module links must include the returnUrl argument. For example, use the Fluid <be:moduleLink> ViewHelper to include this argument:

Benefits

This feature improves navigation for users by enabling easy return to the previous module or a custom page, enhancing the backend user experience.

In TYPO3 v13.3, the typo3conf directory is no longer required in Composer Mode. The Environment and Install Tool will no longer check for its existence. Previously, it stored:

Key Highlight

• Extensions (now managed in vendor/)
• Configuration files (now moved to config/)
• Language labels and artifact states (moved to var/)
• Backend lock file (LOCK_BACKEND)

Benefits

This change simplifies the TYPO3 directory structure.

TYPO3 v13.3 introduces a new configuration setting to define the location of the backend locking file, previously stored in typo3conf/. The new setting $GLOBALS['TYPO3_CONF_VARS']['BE']['lockBackendFile'] allows you to specify the location of the LOCK_BACKEND file.

Default Locations

• Composer Mode: var/lock/
• Legacy Mode: config/
• If you used a custom location or automation for the LOCK_BACKEND file, update your processes or use CLI commands (vendor/bin/typo3 backend:lock and vendor/bin/typo3 backend:unlock).

Benefits

The new setting provides flexibility for managing the backend locking file location, now defaulting to var/lock/ (Composer) or config/ (Legacy), and allows for easier management of backend maintenance.

In TYPO3 v13.3, a new API streamlines file upload and deletion for Extbase extensions. This makes handling files within Domain Models easier and more efficient.

Key Features

• Support for FileReference and ObjectStorage<FileReference> properties in Domain Models.
• Flexible validation for file uploads (file count, size, MIME types, and image dimensions).
• Automatic folder creation for file uploads and customizable upload paths.
• New UploadDeleteCheckboxViewHelper simplifies file deletion in forms.

Usage Example

Benefits

For extension developers, this update reduces complexity while ensuring data integrity through strict validation before file uploads are processed.

GIFBUILDER now supports the AVIF image format, known for better compression and smaller file sizes compared to JPG. AVIF is compatible with most modern browsers, but be sure to verify your operating system’s support for AVIF encoding, as some systems like Debian 11 may lack it.

You can set AVIF as the output format using format=avif in your TypoScript configuration. Image quality and speed can also be adjusted via $TYPO3_CONF_VARS or TypoScript properties.

Usage Example

In Fluid 4, comments created with <f:comment> are now removed before template parsing, thanks to the new RemoveCommentsTemplateProcessor. This allows developers to include invalid Fluid code within <f:comment> without causing errors, while keeping line breaks intact for accurate error referencing.

Benefits

This improvement simplifies template development, as developers no longer need to ensure that commented-out code is valid Fluid syntax.

TYPO3 v13.3 simplifies content element creation by automatically adding system fields like language, hidden, etc., to all content types (CTypes). Previously, these fields had to be manually added to each element’s definition.

Usage Example

Benefits

System fields are now automatically included based on the control definition (ctrl) of the content type. This reduces the configuration effort and unifies the editor form. Custom fields remain after the general palette, and custom labels for system fields are no longer preserved.

TYPO3 v13.3 introduces improved HTTP response headers for frontend rendering. When pages are client-cacheable, a new TypoScript option config.sendCacheHeadersForSharedCaches = auto ensures better handling of proxies and CDNs. It caches content in shared caches like reverse proxies while keeping the browser’s cache fresh.

Usage Example

// TypoScript
config.sendCacheHeaders = 1

Benefits

This update allows TYPO3 to instruct shared caches (e.g., CDNs) to store cached responses, while delivering up-to-date content to users. The new setting takes precedence over the existing config.sendCacheHeaders = 1 when behind a reverse proxy.

TYPO3 v13.3 adds more fields to the Link Validator, including pages.canonical_link, sys_redirect.target, and sys_file_reference.link. This helps catch broken links in these fields automatically.

Benefits

These fields are now part of the default link checking process. Note that pages.canonical_link requires the SEO extension to be installed for validation. Additional system fields are available for custom configurations but are not included by default.

TYPO3 v13.3 introduces a new opacity option in the TCA color picker, allowing colors to be defined with transparency using RRGGBBAA notation.

Usage Example

Benefits

With opacity enabled, editors can now select both a color and its transparency directly in the color picker element.

TYPO3 v13.3 adds an external flag to the AssetCollector options. When enabled, asset files added via $assetCollector->addStyleSheet() or $assetCollector->addJavaScript() bypass URI processing like cache busting.

Usage Example

This feature allows developers to include CSS and JavaScript files with their original URIs, skipping additional processing.

TYPO3’s ExpressionBuilder now features a new method for creating "if-then-else" expressions, which automatically translates to IF or CASE statements depending on the database engine. Additionally, a new method allows casting results to text-like data types, simplifying the conversion of non-text values within complex expressions.

These updates help extension developers build advanced queries more efficiently and ensure better compatibility across different database systems.

TYPO3 v13.3 introduces automatic cache tagging for frontend content. Now, cache entries are tagged with the database records they use. When these records are updated in the backend, the relevant cache entries are automatically invalidated.

This enhancement simplifies cache management, removing the need for manual configuration of cache tagging and eviction. The feature, enabled by default in new TYPO3 v13 installations, must be manually activated in upgraded instances via the frontend.cache.autoTagging toggle.

Benefits

With automatic cache tagging, cache entries are consistently updated as records change, streamlining cache management and ensuring accurate content delivery.

TYPO3 version 13.3 is the final release before the v13 LTS in October 2024. With this release, no new features will be added; instead, the focus is on testing, polishing, and refining existing features. Key tasks include finalizing Content Blocks functionality and integrating backend user permission presets.

TYPO3 Extension developers are encouraged to review and update their extensions for TYPO3 v13 compatibility to ensure smooth adoption of the upcoming LTS release.

• Deprecation: #101559 - Extbase uses ext:core ViewInterface
• Deprecation: #102422 - TypoScriptFrontendController->addCacheTags() and ->getPageCacheTags()
• Deprecation: #102821 - ExtensionManagementUtility::addPItoST43()
• Deprecation: #104223 - Fluid standalone methods
• Deprecation: #104304 - BackendUtility::getTcaFieldConfiguration
• Deprecation: #104325 - DiffUtility->makeDiffDisplay()
• Deprecation: #104463 - Fluid standalone overrideArgument
• Deprecation: #104607 - BackendUserAuthentication:returnWebmounts()
• Deprecation: #104662 - BackendUtility thumbCode
• Deprecation: #104684 - Fluid RenderingContext->getRequest()
• Deprecation: #104764 - Fluid TemplatePaths->fillDefaultsByPackageName
• Deprecation: #104773 - Custom fluid views and extbase
• Deprecation: #104773 - ext:backend LoginProviderInterface changes
• Deprecation: #104778 - Instantiation of IconRegistry in ext_localconf.php
• Deprecation: #104789 - Fluid variables true, false, null
• Deprecation: #104789 - renderStatic() for Fluid ViewHelpers

Exciting Update! Starting with TYPO3 v13.0, the core team is focusing on introducing new features with well-defined migration paths to ensure a smooth transition towards the LTS release. Moving forward from TYPO3 v13.0, the community aims to build on a stable foundation, minimizing major changes to enhance user experience on the path to LTS.

TYPO3 version 13 introduces updated system requirements to support future enhancements and ensure compatibility with modern, long-term supported packages.

With TYPO3 v13, PHP version 8.2 is now required, providing security updates until December 2025. This PHP version is also essential for Symfony v7, a key component of TYPO3 v13, which will be supported until November 2028.

Support Timeline
Each TYPO3 sprint release (from v13.0 to v13.3) will be supported until the next minor version is released. TYPO3 v13 LTS (version 13.4), the long-term support edition, will receive bug fixes until April 30, 2026, with security patches available until October 31, 2027.

Further Details
For more information on requirements and dependencies, visit get.typo3.org. These measures ensure TYPO3 remains up-to-date, secure, and well-supported for users and developers.

For comprehensive details on TYPO3 v13.3, including download and installation instructions, visit get.typo3.org. The Installation Guide provides step-by-step instructions to assist you through the process.

We recommend using Composer for an optimal and streamlined setup. Check out these resources to ensure a smooth installation experience.

TYPO3 version 13.4, the long-term support release (LTS), is set for 15 October 2024. TYPO3 people  finalizing a few remaining features and tasks. Watch for announcements about release parties, online events, and demos to celebrate the launch of TYPO3’s latest flagship version.

TYPO3 version 13.3 marks a significant step forward with its innovative features and adaptability. This release underscores TYPO3’s commitment to technological advancement and progress.

But our journey doesn’t end here. We invite the TYPO3 community and beyond to dive in, contribute, and help shape TYPO3’s future. The insights shared here are drawn from the official documentation, and I’m grateful to the incredible TYPO3 Community for their support.

A Few Final Thoughts:

• Gratitude: A heartfelt thanks to the TYPO3 Open Source community for their invaluable contributions. Show your appreciation on social media, in Slack groups, or consider making a donation to TYPO3.
• Keep Exploring: Install TYPO3 v13.3 and start exploring how these updates can enhance your projects or extensions. If you face challenges or have ideas, share them on TYPO3 Forge.

Have a Happy TYPO3 Release!