TYPO3 Version 11 Roadmap
| Version | Focus of development | Release date |
|---|---|---|
| 11.0 | New system requirements and breaking changes | 22.12.2020 |
| 11.1 | Multi-factor authentication | 23.02.2021 |
| 11.2 | Link sharing in the TYPO3 backend | 04.05.2021 |
| 11.3 | tbd | 13.07.2021 |
| 11.4 | Feature freeze | 07.09.2021 |
| 11.5 | LTS release | 05.10.2021 |
Version 11.0 (sprint release, published on 22.12.2020)
As every "point zero" release focuses on clean-up work, TYPO3 version 11.0 introduces a large number of ground-breaking changes. Here we have picked out a few highlights that you can look forward to in the latest version.
Let's start with a brief summary of the overall plans for the TYPO3 v11 series. As a reminder, what follows is the agenda for the months leading up to October 2021. Version 11.0 lays the foundation for achieving these goals, with new features to be added in the upcoming sprint releases.
The goals in TYPO3 11
The 11th major version of the open source content management system TYPO3 shows the maturity and continued success of the system. (It's actually technically the 8th version, as it started with version 3 and skipped version 5, but that's another story).
With a strong focus on accessibility for the TYPO3 backend, the experience for editors and administrators in TYPO3 v11 should be improved even further. From a technical perspective, simplified authentication has been set as an important goal; under the hood, some changes and improvements have already been made in version 11.0.
Benni Mack (TYPO3 Core Project Lead) presented the general goals, the minimum technical requirements and the planned release schedule a few weeks ago in his article "A First Glimpse of TYPO3 v11". Based on his overview, the most important features we are likely to see in the coming months are as follows:
- Link sharing and "deep linking" for the TYPO3 backend
- Multi-factor authentication (MFA)
- Improved TYPO3 backend experience
- Improved Extbase framework
- Improved authentication process
As part of the development of TYPO3 v11, several libraries that TYPO3 depends on will be (or have already been) updated:
- Doctrine DBAL version 3.0
- Symfony version 5.2+
- Bootstrap version 5 (for the TYPO3 backend)
- Composer version 2 (for Composer-based installations)
The most important changes in TYPO3 11.0
General
By adhering to a strict deprecation policy, the aim is to ensure that TYPO3 is and remains a stable, robust and reliable enterprise content management system. Except in rare cases, no groundbreaking changes (such as new APIs or removed components) are included in minor or bugfix releases. As mentioned above, a "point zero" release allows new libraries and modern concepts to be introduced. The streamlining of APIs and the adoption of even better-known and more established software standards are also opportunities that should be exploited in the first sprint release.
Bootstrap 5 in the TYPO3 backend
As part of a visual refresh, the TYPO3 backend has been upgraded from Bootstrap 3 to 5. First released in 2011, Bootstrap is now the world's most popular frontend open source toolkit. The decision to use version 5 puts TYPO3 at the forefront of modern content management systems from a UI perspective.
Backend users do not have to familiarize themselves with a new user interface with Bootstrap 5. However, you might notice a few minor changes in the usability of TYPO3 v11.0. The new Bootstrap version also brings some accessibility improvements to the TYPO3 backend.
Cleaning up old redirects (redirects)
Redirects typically have the goal of redirecting your website visitors from an old to a new destination - for example, a page. In many cases, these redirects are only needed for a certain period of time. Site administrators can now configure TYPO3 to automatically remove redirects based on certain criteria, such as their age, domain or number of hits. Backend users (e.g. editors with appropriate access rights) can mark redirects as "protected" to prevent them from being deleted.
Session handling
As part of the already mentioned improvement of the authentication process, some components of the TYPO3 core responsible for user authentication in the frontend and backend have been revised. In previous versions of TYPO3, the handling of user sessions was part of the user authentication components of the TYPO3 core. These were revised in TYPO3 v11.0 and separated into the user object, the authentication process and the session handling.
A separate API has been created for session handling, which offers core and extension developers centralized handling of sessions. The new UserSession object contains all session-related data. Developers should use the UserSessionManager to create new sessions.
Workspaces (working environments)
The "Workspaces" function is one of the unique selling points of TYPO3. Workspaces allow editors to collaborate on versioned content on a TYPO3 website and review pages before publishing. At the most basic level, you can configure permissions so that backend users can only edit content in an isolated workspace. Each change must be approved by a supervisor, giving you full control over what content goes live and when. However, TYPO3's workspaces are often overlooked.
TYPO3 v11.0 has started to improve the underlying code and clarify some conceptual issues. In future releases, the existing functionality will be stabilized, the documentation updated, the user-friendliness improved and new functions introduced.
PSR Standards
It cannot be emphasized often enough how important uniform standards are. Coding guidelines and following official recommendations are intended to ensure that the TYPO3 core architecture meets the highest standards and uses state-of-the-art technologies. The "PHP Framework Interop Group" issues and publishes just such standards: the well-known PSR standards. A large number of these have already been adopted and PSR-11 ContainerInterface, PSR-14 EventDispatchers and PSR-15 Middlewares were introduced in earlier TYPO3 versions.
PSR-7 and PSR-17 are also not new in the TYPO3 world. These standards describe common interfaces for displaying HTTP messages. In simple terms: how PHP applications receive and generate HTTP requests and how they should react to them.
The TYPO3 core is continuously improved according to these standards and the PSR-7 request/response objects for extension developers and integrators have been made available in even more places - for example in self-developed content objects ("cObjects").
Extbase Framework
This initiative also affects the Extbase framework. To comply with PSR standards, controller actions should from now on return an instance of the "Psr\Http\Message\ResponseInterface".
It may sound like a big task for extension developers to update their existing code. However, the benefits are obvious. Developers will have much more control over the responses and with the ResponseFactory it is easy to customize the response even further.
It is certainly important to know that the typical old ResponseInterface behavior (not returning anything) triggers a deprecation warning in TYPO3 v11, which you can find in the logs. Nevertheless, it will continue to work for now and there is enough time to update your code before it produces an error in TYPO3 v12.
Fluid widgets
A special type of ViewHelpers in Fluid are "widgets". Logically, they are part of the view, but widgets have their own controller and view. Strictly speaking, the technique violates the "separation of concern" design pattern and causes problems when using PSR-7 request objects in Extbase.
It was therefore decided to drop Fluid ViewHelper widgets, and TYPO3 v11 no longer supports them. A prominent use case of a Fluid widget in TYPO3 Core is the <f:paginate...> ViewHelper. We advise developers to rework their extensions and use the Pagination API instead.
Dependency injection
Developers should also monitor the development of Extbase's Dependency Injection (DI). The plan is to deprecate and remove the current implementation in Extbase and instead use the feature offered by the TYPO3 core. This solution is based on the PSR-11 standard and includes the industry-proven DI concepts of Symfony.
Simplified upgrades
A fast and straightforward upgrade path from older versions of TYPO3 is one of the goals defined in the overall strategy for v11.
It is strongly recommended to use TYPO3's Extension Scanner (Admin Tools → Upgrade → Scan Extension Files) to identify potential issues before upgrading. Typical problems are self-developed extensions that use APIs that are outdated or have been removed. The Extension Scanner provides useful and comprehensive instructions for developers on how to update the code.
If you are upgrading from TYPO3 v9 or v10 to v11, use the upgrade wizard as described in the installation and upgrade guide. This critical step of the upgrade process takes care of various migration tasks, such as content updates and global configuration changes, if required.
System requirements
TYPO3 v11 requires PHP version 7.4 or higher. The Doctrine DBAL used by the TYPO3 core ensures that a wide range of database servers and database engines are supported. These include MySQL version 5.7.9 or higher, MariaDB version 10.2.7 or higher, PostgreSQL version 9.4 or higher, Microsoft's SQL Server 2012 or higher and SQLite version 3 (bundled with PHP).
TYPO3 v11 supports all modern web servers, including Apache 2.4, Nginx and IIS.
Users can access the backend of TYPO3 v11 with all modern browsers, such as Mozilla Firefox, Microsoft Edge (Chromium-based only), Google Chrome and Chrome for Android, Safari and Mobile Safari.
Version 11.1 (sprint release, published on 23.02.2021)
Perfectly on schedule and equipped with the expected features, TYPO3 v11.1 marks another milestone on the way to the TYPO3 v11 LTS release. The following sections focus on the most important changes, improvements and features. Further details can be found in the TYPO3 What's New slides and in the detailed technical changelog.
Multi-factor authentication (MFA)
When you log into the TYPO3 backend, you control a wide range of functions. Depending on the access level, you can edit the content of your company's online presence, change business-critical data or access highly sensitive user information. This data must be protected so that only you have access to it.
Sometimes a username and password are simply not secure enough. Multi-factor authentication (MFA) remedies this by including a second or even multiple factors in the login process. The use of two factors is also known as two-factor authentication (2FA). When implemented correctly, MFA makes it much more difficult for an attacker to gain unauthorized access. For this reason, MFA is considered one of the most effective security measures in information systems today.
When introducing an additional authentication method, it is important to consider the users. If the login process becomes too cumbersome and complicated, users will not use it and miss out on an increased level of security.
With users in mind, a modern, secure, easy-to-use and flexible MFA solution has been implemented in TYPO3 version 11.1.
Once an administrator has activated an MFA provider, backend users can use it as a second authentication method for their login process. Typical providers are, for example, the time-based one-time password (TOTP), the counter-based one-time password or WebAuthn. WebAuthn is a modern web standard that was published by the World Wide Web Consortium (W3C) and is supported by modern versions of the Chrome, Firefox and Edge browsers.
Resizing/switching the navigation area
The navigation area has had a fixed width since TYPO3 version 8. This area is the second column from the left in the backend, in which the page tree (when calling up modules under the heading "Web") or the file list (heading "File") is displayed. Sometimes the fixed width led to problems. In TYPO3 instances with long page titles and page trees with many levels, the content was cut off in this area.
This component would be revised and a resizable navigation area would be reintroduced in TYPO3 version 11.1.
The button for collapsing and reopening the navigation area within the panel has been moved. This placement is now more suitable from a user-friendliness point of view. You do not have to reset the width of the navigation area every time you log in to the backend. TYPO3 remembers the last setting and restores the previous state the next time you log in.
By using the CSS/Flexbox framework, browsers now load the TYPO3 backend faster. In addition, less data is transferred between TYPO3 and the client, which improves performance.
Working with the file list
The "File List" module has been visually redesigned in TYPO3 v11.1. By using the same lightweight technologies as the page tree, both components now have a uniform look and feel. This change also means that the iframe previously used by the module has been removed.
The main benefit is a speed improvement but you will also notice an input field at the top. This field allows you to filter the folder list based on search terms, similar to the page tree filter that many backend users are used to from the page tree. The search in the file list even takes the file names into account.
Accessibility improvements
TYPO3 developers are constantly striving to improve accessibility so that people with different hearing, mobility, visual and cognitive abilities can use the TYPO3 backend.
Following the suggestions of WAI-ARIA Authoring Practices 1.1, users can now navigate through the main module menu and the help menu using only their keyboard. This group includes users with screen readers or similar assistive technology.
Another accessibility improvement is that you can now set an alt tag for a custom backend login screen.
Version 11.2 (sprint release, published on 04.05.2021)
SVG-based page and file tree "everywhere"
In TYPO3 v9, the page tree was reworked, switched to a pure SVG approach and all ExtJS code was removed from the backend. This led to greatly improved rendering times and made working in the page tree much smoother. This area was further optimized in v10 and at the beginning of the year the backend module "Filelist" was revised in TYPO3 v11.1. Since then, the file list has used the same lightweight technology as the page tree.
Both components, the page tree and the file/folder list, also appear in the "Record Selector". This is the modal window where users can select a page, file, folder, external URL or email address etc. The Record Selector now has the same modern components and architecture as the page tree and file/folder list.
For example, users can apply a filter and collapse the tree component. Content elements are now much easier to find and select. They appear clearly listed in the content area. The user can filter the folder list using search terms via an input field at the top. TYPO3 even takes file names into account and displays a list of folders containing files that match the pattern specified by the user.
This uses SVG technology, which is light and lean and renders very quickly in all modern browsers. Since the data is loaded using JSON-based AJAX, only the required parts of the trees are fetched from the server. The same applies to the content area, which leads to an incredible performance boost when working in the backend.
Whenever a tree component (page or file tree) comes into play, its visual appearance and functions are now consistent throughout the TYPO3 backend. Backend users can even navigate within the tree components using their keyboard.
"Deep linking" in the backend
Deep links are nothing unusual in the frontend. For example, if you are interested in becoming a member of the TYPO3 Association, visit the typo3.org website and navigate to the corresponding page. You will end up at typo3.org/project/association/membership. This link represents the path to the web content on the website. You can bookmark this link in your browser and/or send it to your colleagues.
Users now also have this option when working in the TYPO3 backend.
If two or more editors are responsible for maintaining the content of a website, they can now simply point their colleagues to a specific target in the backend. This is not limited to one page. Backend users can, for example, share a deep link to a specific content element.
Backend users who frequently update the same content on a page now have the option of saving the link as a bookmark and opening it directly. If they are not yet logged into the backend, the login form appears and the user is automatically forwarded to the correct destination after successful authentication.
Anyone who has experience with TYPO3 often has to guide a newcomer or customer through the backend. Sometimes in an email, sometimes remotely on the phone. Do instructions like the following sound familiar?
"Please find the 'Web' module in the backend on the left-hand side and then click on 'List'. Now select the page 'Star Trek Actors' from the page tree. If you do not know where the page is located in the page tree, enter the name in the search field. Once you have clicked on the page, search for the table 'Voyager' in the content area. Then ..."
That's all history now. Integrators and customers can simply share a deep link. The recipient follows the link and ends up in the right place. Quick and easy.
Site Configuration: System Locales
System locales are used to localize different formats throughout the system. The locales are generated on the server and are basically conventions for the use of date and time formatting, currency display, etc.
In older versions of the CMS, TYPO3 integrators had to manually enter the locale identifier when setting up a new site for their instance. To speed up the setup of a site and its languages, TYPO3 v11.2 now recognizes which locales are available on the system and lists them in a dropdown box.
Integrators can now simply select the appropriate element from the list, saving time and reducing the chance of errors.
Updating certain components
Sprint releases are a perfect opportunity to update libraries and tools used in TYPO3. Introducing new versions early in the lifecycle of a release allows developers to thoroughly use and test them before the Long-Term Support (LTS) release.
In TYPO3 v11.2, the CKEditor has been updated to version 4.16 and Bootstrap from v5-beta2 to beta3. Compatibility with Doctrine DBAL version 2.13 has also been added.
Composer
The installation of TYPO3 with the help of Composer has been the official recommendation for some time now. The advantages are obvious. Composer is not only the de facto standard when it comes to modern dependency management in today's PHP universe. It also makes your life easier when developing, testing, publishing and maintaining your extension and/or installing and updating a TYPO3 instance.
TYPO3 version 11.2 has started to set the course for the future. The long-term strategy is to move away from the proprietary ext_emconf.php files that are currently used by every system and third-party extension.
If you are a TYPO3 developer, make sure your extensions contain a valid composer.json file. This will pave the way to avoid potential problems in the future. An extension without Composer support is considered bad practice, and extensions also need a valid composer.json file to display their documentation on docs.typo3.org. You can read how easy it is to add Composer support in the TYPO3 documentation.
Version 11.3 (sprint release, published on 13.07.2021)
This version contains a number of backend improvements and is now compatible with PHP version 8.0.
User Experience (UX) is about how users interact with a system or web interface. Several areas of the TYPO3 backend have been revised, in particular the list view, which users can access via the Web → List module.
The following sections focus on the most important changes, improvements and functions. Further details can be found in the "TYPO3 What's New" slides and in the detailed technical changelog.
Selectable columns
The list module allows backend users to work with different database entries. Users can now simply select the columns to be displayed in the list. This was only possible in the "Single Table View" in older TYPO3 versions. The updated user interface makes it much easier for users to add and remove columns.
TYPO3 integrators can customize the view with a few lines of User TSconfig and disable the "column selector" for specific or all tables as needed.
Extended view
The list module has an extended view to access additional functions, such as displaying additional details or viewing the change history of content elements. These functions are secondary actions that backend users rarely need in their daily work. Previously, the extended view was activated via a checkbox, which then applied the view to all tables on the page.
With TYPO3 version 11.3, the checkbox has been removed and users can call up the secondary functions for each table individually (via the button with the three vertical dots).
Download data
Did you know that backend users can download almost all database tables as CSV files from the list module? Of course, this requires appropriate access rights to the tables. This "export" functionality has long been part of the TYPO3 core, but has sometimes been overlooked by users.
In TYPO3 v11.3, the download button is now prominently displayed in the header of each table. Instead of a simple CSV download, backend users can now customize the export. In a dialog box, users can configure the file name and format (CSV or JSON) as well as other settings.
Share and pass on backend links
There was a lot of positive feedback when "backend deep links" were introduced in the last TYPO3 sprint release. Sharing links in TYPO3 v11.3 has been simplified even further: copying a link to the clipboard requires only two mouse clicks.
On all pages where deep linking is possible, backend users can click on the share button to open a context menu. In addition to the function to create an internal TYPO3 bookmark, users can copy the link of the current backend page to their clipboard.
Selection of files and data records
Earlier TYPO3 v11 sprint releases already received some improvements for the page and file tree as well as for the record selector. These components now feature fast and lightweight techniques such as the underlying SVG-based code. In TYPO3 v11.3, another area has been revised: the selection of files and records from a list.
Example: adding images to a page using the "Text and Media" content element. The "Add media file" button displays a modal window for selecting one or more files from a list. Backend users can now select a checkbox on the left for each file or open a context menu and select or deselect all items with one click. They can also toggle the current selection.
This functionality can also be found in another frequently used area of the TYPO3 backend: the file list module. Further areas are expected to follow in the next sprint release.
"File" Viewhelper
The "File" ViewHelper is also interesting for developers. The new ViewHelper can be used to create links to files via the File Abstraction Layer (FAL). It is not only very flexible, but also recognizes whether users can access the link target directly (e.g. documents that editors have uploaded to the "fileadmin/" area). In these cases, the ViewHelper generates a direct download link. If the resource is not publicly accessible, the file dump functionality comes into play. This allows extension authors to implement their own solutions, e.g. additional authentication logic.
The "File" ViewHelper also accepts attributes to force a download and to specify alternative download file names.
Extbase: PSR-7 Request/Response
Already in previous TYPO3 releases, uniform standards and state-of-the-art technologies for developers were implemented by following known PSR standards.
As many TYPO3 developers know, Extbase is the object-oriented PHP framework that is heavily used by the TYPO3 core and for extension development. Since extension developers often access information about the current request in their own code, clean PSR-7 request/response handling is important. To enable developers to do this, Extbase now implements a "ServerRequestInterface". The details are all available via $this->request within Extbase controllers.
This change also leads to a unified class "\TYPO3\CMS\Extbase\Mvc\Request" and to some deprecations, for example the methods getRequestUri() and getBaseUri().
Login throttling
Security is another area that is constantly being reviewed and improved in TYPO3. TYPO3 now limits backend and frontend logins using the Symfony library "Rate Limiter". This approach replaces the previous method, which was not a state-of-the-art implementation from a security perspective. A PSR-15 middleware now uses the Rate Limiter to block further authentication attempts if too many failed logins from the same IP address are detected.
Internationalization
The TYPO3 backend now supports two new languages: The Shona (Bantu) language (ISO 639-1 code "sn") and Welsh (ISO 639-1 code "cy"). Shona is the language of the Shona people of Zimbabwe and is spoken by more than 10 million people, including dialects. Welsh (historically known as "Cymbric") was originally spoken in Wales.
It is now possible to download translated backend labels from the TYPO3 translation server and CrowdIn for these languages, switch the backend interface to Shona and Welsh respectively, and use these languages in site configurations.
Version 11.4 (sprint release, published on 07.09.2021)
This release marks the last phase of the v11 development cycle before the TYPO3 v11 LTS release. Read on to learn more about the last sprint release of the v11 series and what "feature freeze" really means.
We are confident that the TYPO3 v11.4 release is stable and can be used in most projects. The core developers, contributors and testers have spent a lot of time and energy to stabilize the system and make it robust and secure.
File list" module
Working with the File List backend module is now faster and easier than ever before. Each item in the file/folder list has a checkbox on the left-hand side. Backend users can now check and uncheck items, toggle selections, and easily perform actions such as editing metadata or deleting a file.
In previous TYPO3 versions, users had to transfer items to the TYPO3 clipboard before they could work with multiple files at once. In TYPO3 v11.4, the selection of items in the file list has been decoupled from the clipboard logic. The buttons to perform various actions appear as soon as the first element has been selected.
In addition to editing the metadata of a file and deleting a file, a new action has also been introduced. Backend users can now download multiple files or folders at once by instructing TYPO3 to create a ZIP archive of them.
In TYPO3 v11.3, the "selectable columns" feature has been added to the list view. The same feature is now available in the file list module. Backend users can simply select the columns to be displayed in the list.
Column selection filter
The column selection in the record and file list now has a filter at the top. Backend users can enter a few letters in the input field to easily find the columns they want to add or remove from the list. This filter is very useful for tables with many columns.
Work more efficiently with the keyboard
Many users are convinced that they can select and deselect list items more efficiently when using their mouse and keyboard. Keyboard enthusiasts will be happy to hear that the record and file list now supports some keyboard shortcuts to speed up interaction. For example, hold down the Shift key while clicking on the first and last item you want to select. This will automatically select all items in between. Use the Ctrl/Option key to toggle the current selection.
Improved Workspaces module
The first sprint release of the v11 series - TYPO3 version 11.0, which was released in December 2020 - included some changes and adjustments to the backend module "Workspaces". In the release announcement, it was pointed out that workspaces are one of TYPO3's unique selling points. This underlines the importance of the module and its functionality.
As planned, the backend module has been further improved. These include Ajax requests, which ensure a better user experience and shorter loading times. Backend users can now switch between workspaces via a drop-down menu at the top of the module. The overall look and feel is now more in line with the other areas of the TYPO3 backend. In addition, website administrators can now access the settings directly from the module header.
When reviewing changes in a large workspace environment, backend users are sometimes faced with a long list to go through. This can be confusing and confusing. A new drop-down menu in the Workspaces module allows users to filter items by a specific level, e.g. "Ready to publish". The reduced list (which incidentally only contains the available/relevant stages of the current workspace) helps users to focus on their specific task.
Language switching in the page module
The way users interact with the backend when working with frontend languages has been slightly changed in the new TYPO3 version. With the backend module Web → Page, users can choose which language or translation of a page and page content they want to edit. In previous TYPO3 versions, the default language (e.g. "English") displayed all content elements of all languages.
To simplify the work for editors and translators, the selected language only shows the content elements of this language. With the new "All languages" option, users can access all content elements in all languages if required.
Changes for integrators and developers
As with every other TYPO3 release, there are also changes for integrators and developers in version 11.4. However, due to the feature freeze, the focus is more on stabilizing the existing code base than on introducing new important features and APIs.
The top priority for a feature freeze release is a robust foundation. This is more important than adding more libraries and technologies to the system. Nevertheless, TYPO3 version 11.4 also contains some improvements and exciting new features for developers.
JsonView
The Extbase JsonView offers a convenient way to output data in JSON format. Typical use cases for this view are Ajax requests and RESTful APIs.
To reduce the configuration effort for developers, the JsonView now accepts the "_recursive" property. This recursive conversion of properties eliminates the need to manually define each level. Developers can now easily apply this property to e.g. output comments that contain other comments as responses.
Extbase ObjectManager
Since the introduction of Symfony's DependencyInjection component in TYPO3 v10 LTS, extension developers have been advised to use this modern implementation, which follows the PSR-11 standard. Now is a good time to deprecate the Extbase ObjectManager to prepare it for removal in TYPO3 v12. This means that developers should no longer call the "ObjectManager->get()" function, for example.
Improvements in Composer mode
TYPO3 version 11.2 set the course for the future in terms of managing extensions with the PHP-based Dependency Manager Composer.
In TYPO3 version 11.4, another big step forward was taken and the well-known "PackageStates.php" file was abolished for Composer-based TYPO3 installations. This file stored the information about active packages in the system. Since the same information is managed by Composer, this change eliminated redundancy. All extensions that Composer adds to the system are now considered active. This also made it possible to remove the functions for activating and deactivating extensions from the Extension Manager and also from the TYPO3 CLI.
To set up a newly added extension with Composer, it is recommended to also execute the TYPO3 CLI command "extension:setup", e.g. to perform database schema updates.
It was already mentioned in the TYPO3 v11.2 release announcement that the proprietary ext_emconf.php file is to be abolished in the future. The changes mentioned above are intended to achieve exactly that. Composer-based TYPO3 installations do not need this file and will even ignore it from now on. However, extension developers can keep this file for the time being if they want to maintain compatibility with TYPO3 instances in non-Composer mode.
It should be noted that these changes only apply to TYPO3 instances that use the Composer-based installation method. This method is the officially recommended way to install TYPO3.
TYPO3 Caches
TYPO3 achieves outstanding performance thanks to its well thought-out caching framework. The TYPO3 Command Line Interface (CLI) is an indispensable tool for automated deployments that are controlled/executed by scripts, for example. Two new commands for the TYPO3 CLI allow integrators and administrators to empty and warm up the caches:
- bin/typo3 cache:flush
- bin/typo3 cache:warmup
HTTPS as standard
The average HTTPS traffic across all platforms was almost 90% in May 2021, according to Google's transparency report. Therefore, it is only logical that an enterprise content management system such as TYPO3 sets "https://" as the default scheme for as many components as possible.
When users enter a URL into the CKEditor (TYPO3's default rich text editor), TYPO3 automatically converts the domain into a link (more specifically, the CKEditor's "AutoLink" plugin does the conversion). The resulting link now uses "https://" as the default schema. Editors can of course also customize the link manually and change the default schema to a different value, for example "http://".
TYPO3 developers and integrators will find a similar function in the Fluid ViewHelpers "<f:link.external>" and "<f:uri.external>". Both use the secure schema by default since TYPO3 v11.4. The parameter "defaultScheme=" can be used to override the default.
Feature Freeze
TYPO3 version 11.4 marks the feature freeze for the v11 cycle according to the roadmap. From this point on, no new features are planned until the LTS release in October 2021. This means that the core team and all contributors will focus on testing, polishing and refining the source code and the system from the time of the feature freeze until the final LTS release. However, some exceptions will allow us to complete and/or improve existing new features that we have recently added.
Pictures: typo3.org