Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[TASK] Deprecate various public TSFE properties
Various properties can be accessed directly via TypoScript config settings. * $TSFE->spamProtectEmailAddresses * $TSFE->intTarget * $TSFE->extTarget * $TSFE->fileTarget * $TSFE->baseUrl They have been marked as deprecated. In addition, some internal functionality is now marked as @internal as well, somehow related to the deprecated properties. Resolves: #97866 Releases: main Change-Id: Ieecd1674783a1d9b9092528d16a988568e857e18 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/75040 Tested-by: core-ci <typo3@b13.com> Tested-by: Stefan Bürk <stefan@buerk.tech> Tested-by: Oliver Bartsch <bo@cedev.de> Tested-by: Benni Mack <benni@typo3.org> Reviewed-by: Stefan Bürk <stefan@buerk.tech> Reviewed-by: Oliver Bartsch <bo@cedev.de> Reviewed-by: Benni Mack <benni@typo3.org>
- Loading branch information
Showing
12 changed files
with
120 additions
and
27 deletions.
There are no files selected for viewing
48 changes: 48 additions & 0 deletions
48
.../Documentation/Changelog/12.0/Deprecation-97866-VariousPublicTSFEProperties.rst
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
.. include:: /Includes.rst.txt | ||
|
||
.. _deprecation-97866-1657185866: | ||
|
||
==================================================== | ||
Deprecation: #97866 - Various public TSFE properties | ||
==================================================== | ||
|
||
See :issue:`97866` | ||
|
||
Description | ||
=========== | ||
|
||
The following properties within TypoScriptFrontendController have been deprecated: | ||
|
||
* :php:`spamProtectEmailAddresses` | ||
* :php:`intTarget` | ||
* :php:`extTarget` | ||
* :php:`fileTarget` | ||
* :php:`baseUrl` | ||
|
||
All of these properties can be accessed through TypoScript's config array. | ||
|
||
|
||
Impact | ||
====== | ||
|
||
Accessing these properties via TypoScript `getData` or via PHP will trigger a PHP deprecation | ||
notice. | ||
|
||
|
||
Affected installations | ||
====================== | ||
|
||
TYPO3 installations with TypoScript options such as :ts:`.data = TSFE:fileTarget` or | ||
TYPO3 installations with third-party extensions accessing the properties via PHP. | ||
|
||
|
||
Migration | ||
========= | ||
|
||
Migrate the access to these properties to use the config property: | ||
|
||
In TypoScript you can access the TypoScript properties directly via | ||
:ts:`.data = TSFE:config|config|fileTarget` and in PHP code via | ||
:php:`$GLOBALS['TSFE']->config['config']['fileTarget']`. | ||
|
||
.. index:: Frontend, TypoScript, PartiallyScanned, ext:frontend |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters