The sprint release version 9.2 focuses on “Site Handling” and will boost the productivity of editors, push the creativity of developers and ease the life of integrators.
The most notable new feature in TYPO3 version 9.2 is the Site Handling functionality. Already introduced in version 9.1, the Site Management module in the backend of TYPO3 now contains a new sub-module “Configuration”. This enables integrators and site administrators to add and modify a global configuration for one or multiple sites.
A site configuration has a unique (human-readable) identifier and configuration values such as the root page ID, the base path (entry point), language definitions, etc. By storing the settings in a YAML file under “typo3conf/sites/site-identifier/”, it is easy to maintain the configuration in a version control system such as Git for example.
The Site Handling functionality already supports configurations such as domains, languages, error-handling and will be extended further until the the v9 LTS release later this year.
The SwiftMailer project provides a sophisticated PHP library, that is the de-facto standard for creating and sending RFC compliant emails in PHP with a multitude of features. SwiftMailer has been integrated in TYPO3 since version 4.5.
With TYPO3 version 9.2, it is now possible to leverage SwiftMailer’s queue functionality - also known as “spool transport”. In most cases, developers want to send out emails immediately, but under certain circumstances, “spooling” emails and processing them later is beneficial, e.g. for performance reasons. Therefore, we are happy to announce, that the Mail API of TYPO3 version 9.2 now supports SwiftMailer’s “SpoolTransport” functionality.
Hardening the Security
TYPO3 stores various files in the “var/” directory, which is typically located under “typo3temp/var/”. Some of these files are for example Install Tool session files, caching framework files, files related to locking or logging, Extension Manager data files or files generated by TYPO3’s import/export or core update functions. Despite the fact that a properly configured web server and TYPO3 instance prevents accessing any sensible files in the “var/” directory, it is obvious that these are non-public files, which should better be located outside the web root. As part of the ongoing effort to enhance the security of TYPO3 even further, the path to the “var/” directory can now be configured as an environment variable TYPO3_PATH_APP. The following configuration directive can be used by the Apache web server for example:
SetEnv TYPO3_PATH_APP /var/www/example.com/
This would instruct TYPO3 to create and use directory “/var/www/example.com/var/” whereas the web root should be “/var/www/example.com/htdocs/”. If the environment variable is not set, non-composer installations of TYPO3 continue to use “typo3temp/var/” as the default. Composer-based installations benefit from this functionality directly, as data is stored within the project roots' folder under “var/”.
To learn more about the new features, changes and improvements of TYPO3 version 9.2, have a look at the TYPO3. The next release on our road to the LTS version of TYPO3 v9 will be version 9.3, currently scheduled to be released in June 2018.