Commit 737af52d authored by Christian Kuhn's avatar Christian Kuhn
Browse files

[TASK] Synchronize core changelog files between v11, v10, v9

The nifty ruleset for handling core changelog files described at
https://docs.typo3.org/c/typo3/cms-core/10.4/en-us/Changelog/Howto.html
sometimes gets violated by the one or the other patch.

This happens, so we occassionally synchronize Changelog
files between versions.

Resolves: #94668
Releases: master, 10.4, 9.5
Change-Id: Ia02af5909687a6f200257b791fee098ced7f32b5
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70154

Tested-by: core-ci's avatarcore-ci <typo3@b13.com>
Tested-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
parent 544c0da4
.. include:: ../../Includes.txt
===================================================
Feature: #89526 - FeatureFlag: newTranslationServer
===================================================
See :issue:`89556`
Description
===========
The feature switch `newTranslationServer` makes it possible for installations to fetch translations from the new translation server.
The new translation server is building labels from Crowdin (https://crowdin.com/project/typo3-cms) instead of the previous translation server based on Pootle (https://translation.typo3.org/).
If you are interested in this topic, join the Crowdin Initiative. All information can be found at https://typo3.org/community/teams/typo3-development/initiatives/localization-with-crowdin/.
It is very simple to provide translations by registering at Crowdin and suggest translations online.
Impact
======
The feature is enabled by default for new installations.
.. index:: Backend, Frontend, ext:core
.. include:: ../../Includes.txt
=====================================================
Important: #88824 - Add cache for error page handling
=====================================================
See :issue:`88824`
Description
===========
In order to prevent possible DoS attacks when the page-based error handler
is used, the content of the 404 error page is now cached in the TYPO3
page cache. Any dynamic content on the error page (e.g. content created
by TypoScript or uncached plugins) will therefore also be cached.
If the 404 error page contains dynamic content, TYPO3 administrators must
ensure that no sensitive data (e.g. username of logged in frontend user)
will be shown on the error page.
If dynamic content is required on the 404 error page, it is recommended
to implement a custom PHP based error handler.
.. index:: Backend, ext:backend
.. include:: ../../Includes.txt
================================================================
Important: #90911 - Package algo26-matthias/idna-convert removed
================================================================
See :issue:`90911`
Description
===========
The TYPO3 core dependency / composer library `algo26-matthias/idna-convert` does not support PHP 7.4
in its currently used version. It has been removed from the composer dependencies and the current used
code is placed into `typo3/sysext/core/Resources/PHP/idna-converter` to support directly usage of
that package.
This makes it possible to use TYPO3 v9 with umlaut domain validation (e.g. also when using EXT:form
with sending an email to someone with a umlaut domain as recipient) in conjunction with TYPO3 v9 and
PHP 7.4.
If the PHP code of the package is used directly by third-party extensions, this will have no further
side effects, as the TYPO3 core still provides the source code, but be aware will not work with
PHP 7.4.
If you like to use the package in a newer version, follow the docs https://idnaconv.net/docs.html
and add the custom PHP code yourself.
If you are using the TYPO3 API `GeneralUtility::idnaEncode()` everything works as before, but now
also with PHP 7.4 support.
.. index:: PHP-API, ext:core
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment