TYPO3 v15 dev-main snapshot ()
This commit is contained in:
@@ -0,0 +1,39 @@
|
||||
.. include:: /Includes.rst.txt
|
||||
|
||||
.. _breaking-82852:
|
||||
|
||||
=========================================================
|
||||
Breaking: #82852 - Exception is thrown on invalid charset
|
||||
=========================================================
|
||||
|
||||
See :issue:`82852`
|
||||
|
||||
Description
|
||||
===========
|
||||
|
||||
The method :php:`\TYPO3\CMS\Core\Charset\CharsetConverter::initCharset()` and
|
||||
consequently all methods in this class calling that method now throw
|
||||
an :php:`\TYPO3\CMS\Core\Charset\UnknownCharsetException` if an unknown
|
||||
charset was provided.
|
||||
|
||||
The :php:`TypoScriptFrontendController` aka TSFE uses this to throw
|
||||
a :php:`\RuntimeException` in case of an invalid :typoscript:`config.metaCharset`.
|
||||
Before this resulted in a blank page instead.
|
||||
|
||||
|
||||
Impact
|
||||
======
|
||||
|
||||
Third party code directly using the :php:`CharsetConverter` class need to be aware of the new exception in case of an invalid charset.
|
||||
|
||||
Sites with an invalid :typoscript:`config.metaCharset` will now see a clear error message.
|
||||
|
||||
|
||||
Migration
|
||||
=========
|
||||
|
||||
Catch the :php:`UnknownCharsetException` of the :php:`CharsetConverter` if necessary.
|
||||
|
||||
Ensure that :typoscript:`config.metaCharset` is set to a known charset.
|
||||
|
||||
.. index:: Frontend, PHP-API, NotScanned
|
||||
Reference in New Issue
Block a user