- Jan 17, 2020
-
-
Alexander Schnitzler authored
This commit introduces a development requirement to phpstan/phpstan to enable static code analysis. A basic configuration file has been added as well to identify most basic errors in the TYPO3 code base. Releases: master Resolves: #90097 Change-Id: I87e11eca6296864fdd7ba8cd109a23b82c27f641 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62851 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Steffen Frese <steffenf14@gmail.com> Tested-by:
Felix P. <f.pachowsky@neusta.de> Tested-by:
Sascha Egerer <sascha@sascha-egerer.de> Tested-by:
Frank Nägler <frank.naegler@typo3.org> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Jörg Bösche <typo3@joergboesche.de> Reviewed-by:
-
- Jan 16, 2020
-
-
Benni Mack authored
OpenSSL was only needed for EXT:rsaauth, so a check in the installer / system maintenance should be avoided. It is now rather a suggestion. Resolves: #83643 Releases: master, 9.5 Change-Id: If62b7fc1ddc211083fa8b4f793019e61cf2046eb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62918 Tested-by:
Susanne Moog <look@susi.dev> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Tobi Kretschmann <tobi@tobishome.de> Reviewed-by:
-
- Dec 19, 2019
-
-
Alexander Schnitzler authored
composer remove --dev rector/rector composer require --dev rector/rector:~0.6 The update of rector brings important bugfixes and enables the installation of the latest version of phpstan/phpstan. Releases: master Resolves: #89918 Change-Id: I406aa56b19e88db23260033023e2c785425aef5e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62599 Tested-by:Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
-
- Dec 13, 2019
-
-
Benni Mack authored
Due to the INTL/ICU bug, which we have seen on various places, Guzzle, which does not cover our edge cases yet, ran in the same issue as our Core versions earlier in 2019. See https://github.com/guzzle/guzzle/issues/2448 https://github.com/guzzle/guzzle/pull/2454 For the time being, lets mark guzzle as incompatible until Guzzle has solved the issue and released a new version, so we can loosen the conflict constraint. Related: #87953 Resolves: #89904 Releases: master, 9.5, 8.7 Change-Id: If64fb9472d046f020c850cd0551beeaf78796b60 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62606 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
-
- Dec 10, 2019
-
-
Benni Mack authored
In order to use the final LTS distributions from Symfony for our latest stable, we need to set proper platform requirements for the root composer.json. Our packages rely on the settings so the base package can properly raise dependencies. Symfony has the requirements due to other PHP bugs (fixed very early already), however using the tarballs in 7.2.0 / 7.0.0 would still work, as the symfony changes only fix issues we dont rely on. v10: 7.2.5 v9: 7.2.5 v8: 7.0.8 Used composer commands: composer config platform.php 7.2.5 composer update --lock Resolves: #89882 Releases: master, 9.5, 8.7 Change-Id: Ib51ec076e643581603fced3ed0daa0de0aadb12c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62565 Tested-by:
Alexander Schnitzler <review.typo3.org@alexanderschnitzler.de> Tested-by:
-
Alexander Schnitzler authored
In order to let rector process tests, the autoloading of all processed classes needs to be intact. In TYPO3 there were a bunch of classes whose namespace were a bit wrong according to PSR-4 and there were some class that didn't fit the PSR-4 standard at all. Classes that could easily be fixed have been fixed. All others have either been registered via a class map in composer.json or they have been excluded from the processing of rector. This change does not apply rector rules to tests, it only enables rector to operate on tests due to fixed autoloading. Releases: master Resolves: #89900 Change-Id: Iaa4a5bb2677a5a9af374d780423d962dcc09ade2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62583 Tested-by:
-
- Dec 03, 2019
-
-
Benni Mack authored
Change-Id: I0e8abdb62a45326896fc75d9872eead478615dce Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62525 Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
-
Susanne Moog authored
composer require --dev typo3/testing-framework:~6.1.0 Also reverts changes to tests for phpunit 8.3 only. Resolves: #89833 Releases: master Change-Id: I834f70452775ea18960da162bb2affe459b8556a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62519 Tested-by:
-
Susanne Moog authored
The testing framework has been reworked and slimmed down. To make use of it, tests had to be adjusted. composer require --dev typo3/testing-framework:"~6.0.0" Resolves: #89815 Releases: master Change-Id: Ib0a8d7436070ef17be96a5f4011f796dd15b09fd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62502 Tested-by:
-
- Dec 02, 2019
-
-
Benni Mack authored
Using the freshly released version 2.6.8 in our packages adds PHP 7.4 support for Fluid Standalone. composer req "typo3fluid/fluid:^2.6.8" Resolves: #89819 Releases: master, 9.5, 8.7 Change-Id: I986b3f8e73e3114af3aef9f65b42c3bf109f9f39 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62504 Reviewed-by:
-
- Nov 29, 2019
-
-
Benni Mack authored
TYPO3 Core now requires at least doctrine/annotations 1.7, effectively helping to upgrade to PHP 7.4. Resolves: #89812 Releases: master, 9.5 Change-Id: I8ca951711bbcb19d935baad67ff69705d8e51aa2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62498 Tested-by:
-
- Nov 28, 2019
-
-
Jan Stockfisch authored
A new Extbase-based plugin is added to TYPO3's Extension "felogin" which can be used as a toggle with custom templates based on Fluid, instead of marker-based templates. A new feature toggle is added to the Settings module for Site Administrators to switch to the newly added felogin extbase plugin, or continuing using the pibase plugin, e.g. for upgrading purposes. Resolves: #84262 Releases: master Change-Id: I9d281912373a078e0403f52b27483dd3e04785f7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61900 Tested-by:
-
- Nov 27, 2019
-
-
Alexander Schnitzler authored
composer require --dev rector/rector:"^0.5.0" This commit introduces the requirement to rector/rector to automatically process code changes by given set of rules. To make this commit more meaningful, a first set "php53" has been processed. Releases: master Resolves: #89785 Change-Id: I6e2ff9654266458ae9fb6800547ff4712b0b66d8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62437 Tested-by:
-
- Nov 26, 2019
-
-
Alexander Schnitzler authored
composer require --dev friendsofphp/php-cs-fixer:"^2.16.1" Raising the version brings support for running the fixer with PHP 7.4. Releases: master, 9.5, 8.7 Resolves: #89776 Change-Id: Ib065b38c606f17c8e58a684e819cc555e493a91f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62433 Tested-by:
-
- Nov 25, 2019
-
-
Alexander Schnitzler authored
- Adjust namespaces of classes according to PSR-4 - Add a classmap for test fixtures Releases: master Resolves: #89706 Change-Id: Iefd73f8039eb3db4de419ecaab13a18f6abb23e2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62341 Tested-by:
Mathias Brodala <mbrodala@pagemachine.de> Reviewed-by:
-
- Nov 22, 2019
-
-
Benni Mack authored
When running composer update --prefer-lowest the abandoned package hoa/core could still be installed via codeception/codeception, which in turn results in issues running our test suite. See https://github.com/hoaproject/Protocol/issues/8 This is also needed for PHP 7.4 compatibility. Resolves: #89736 Releases: master Change-Id: I51d2e73875650222bcf9c829cfc684cefd59b612 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62365 Tested-by:
-
- Nov 21, 2019
-
-
Benni Mack authored
The next version has PHP 7.4 support and was cleaned up a lot. Used composer command: composer req typo3/testing-framework:~5.0.16 \ --update-with-all-dependencies --dev Resolves: #89725 Releases: master Change-Id: Iba181feb693c9ee61b8792cd0d0197c1e3b1f59a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62359 Tested-by: -
Benni Mack authored
TYPO3 Core v10 should rely on Symfony 4.4 (LTS release) and add support for 5.0 automatically. Symfony 4.4 made breaking changes to the Mailer and Mime components which now need adaptions. Used composer command: composer req "symfony/config":"^4.4 || ^5.0" \ "symfony/console":"^4.4 || ^5.0" \ "symfony/dependency-injection":"^4.4 || ^5.0" \ "symfony/expression-language":"^4.4 || ^5.0" \ "symfony/finder":"^4.4 || ^5.0" \ "symfony/mailer":"^4.4 || ^5.0" \ "symfony/mime":"^4.4 || ^5.0" \ "symfony/property-access":"^4.4 || ^5.0" \ "symfony/property-info":"^4.4 || ^5.0" \ "symfony/routing":"^4.4 || ^5.0" \ "symfony/yaml":"^4.4 || ^5.0" --update-with-all-dependencies Loading composer repositories with package information Updating dependencies (including require-dev) Package operations: 0 installs, 27 updates, 0 removals - Updating symfony/polyfill-ctype (v1.11.0 => v1.12.0) - Updating symfony/filesystem (v4.3.1 => v4.4.0) - Updating symfony/config (v4.3.2 => v4.4.0) - Updating symfony/service-contracts (v1.1.2 => v1.1.8) - Updating symfony/polyfill-php73 (v1.11.0 => v1.12.0) - Updating symfony/polyfill-mbstring (v1.11.0 => v1.12.0) - Updating symfony/console (v4.3.1 => v4.4.0) - Updating symfony/dependency-injection (v4.3.2 => v4.4.0) - Updating symfony/var-exporter (v4.3.1 => v4.4.0) - Updating symfony/cache-contracts (v1.1.1 => v1.1.7) - Updating psr/log (1.0.2 => 1.1.2) - Updating symfony/cache (v4.3.1 => v4.4.0) - Updating symfony/expression-language (v4.3.1 => v4.4.0) - Updating symfony/finder (v4.3.3 => v4.4.0) - Updating symfony/polyfill-php72 (v1.11.0 => v1.12.0) - Updating symfony/polyfill-intl-idn (v1.11.0 => v1.12.0) - Updating symfony/mime (v4.3.2 => v4.4.0) - Updating symfony/event-dispatcher-contracts (v1.1.1 => v1.1.7) - Updating symfony/event-dispatcher (v4.3.1 => v4.4.0) - Updating doctrine/lexer (v1.0.1 => 1.2.0) - Updating egulias/email-validator (2.1.9 => 2.1.11) - Updating symfony/mailer (v4.3.2 => v4.4.0) - Updating symfony/inflector (v4.3.1 => v4.4.0) - Updating symfony/property-access (v4.3.1 => v4.4.0) - Updating symfony/property-info (v4.3.1 => v4.4.0) - Updating symfony/routing (v4.3.1 => v4.4.0) - Updating symfony/yaml (v4.3.1 => v4.4.0) Resolves: #89721 Releases: master Change-Id: I834a79e3880b3a7a95429c2fe052657e21599ec7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62354 Tested-by:
-
- Nov 19, 2019
-
-
Alexander Schnitzler authored
composer require nikic/php-parser:"^4.3" Bump version as PHP 5 support is not necessary for TYPO3 version 10 and modern packages like rector/rector need a newer version of nikic/php-parser to work. Releases: master Resolves: #89704 Change-Id: I402714959750b5203a6e0117e5ef84b62229441b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62339 Reviewed-by:
-
- Nov 09, 2019
-
-
Aimeos authored
composer require "psr/http-message":"^1.0" composer require "psr/log":"^1.0" Releases: master Resolves: #89626 Change-Id: Ieeceddba8ea49da1eac66f113f1c22623f479582 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62260 Tested-by: -
Susanne Moog authored
composer require doctrine/dbal:"^2.10" Releases: master Resolves: #89625 Change-Id: I1f0591d2544c34d1785c3cd3ee4b8a6d6643885f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62259 Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
-
- Oct 30, 2019
-
-
Benni Mack authored
A new fluid standalone version 2.6.6 reverted the changes that had regressions in v2.6.5 and v2.6.4. Composer command: composer req typo3fluid/fluid:^2.6.6 Resolves: #89542 Releases: master, 9.5, 8.7 Change-Id: I30a29a3cc07a277bd4a72e83a67a6c3260adc5d7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62156 Tested-by:
-
- Oct 23, 2019
-
-
Anja Leichsenring authored
A failing nightly test is fixed by avoiding the fluid version to be raised until the cause can be resolved. Resolves: #89480 Releases: master, 9.5 Change-Id: I65329b1ea08c2fbf46766cb82365a7e4275b99c7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62050 Tested-by:
Richard Haeser <richard@maxserv.com> Reviewed-by:
-
- Oct 18, 2019
-
-
Oliver Hader authored
Ensure PHP 7.4 compatibility by using recent release of the package. composer require typo3/phar-stream-wrapper:^3.1.3 Resolves: #89453 Releases: master, 9.5, 8.7 Change-Id: I025bf2efae45b731e1f068afc5fa1d56e1e59a56 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62017 Tested-by:
-
- Oct 01, 2019
-
-
Oliver Hader authored
Change-Id: I81e89208e45b689b32f5c8df2392e8c2b24b8392 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61870 Tested-by:
-
- Sep 24, 2019
-
-
Benjamin Franzke authored
The implementation of the PSR-18 ClientInterface is provided as an adapter to the existing GuzzleHTTP Client. Therefore existing configuraton settings will be reused. As our current Guzzle wrapper (RequestFactory->request) has support for passing custom guzzle per-request options, we do not deprecate this method but add the PSR-18 implementation as a more generic alternative. Once GuzzleHTTP supports PSR-18 natively we can (and will) drop our adapter and point to Guzzles native implementation in our dependency injection configuration. Therefore, this adapter is marked as internal and extensions are being instructed to depend on the PSR-18 interfaces only. composer require psr/http-client:^1.0 Releases: master Resolves: #89216 Change-Id: I0f2c81916a2f5e4b40abd6f0b146440ef155cf00 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61567 Tested-by:
-
Sybille Peters authored
Resolves: #82850 Releases: master, 9.5 Change-Id: I05dc5e83199d58b23a8da6e625d1b9557b5c57a2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61712 Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
-
- Sep 23, 2019
-
-
Claus Due authored
Addresses the following issues: * Fixes an annotation that makes phpdocumentor/reflection-docblock throw exceptions in TYPO3v10. * Removes deprecation warning from composer due to incorrectly cased package name. * Fixes issues with binary characters in compiled templates. * Supports overloaded methods for variable extraction. * Avoids signature issues with CompileWithRenderStatic. * Works around PCRE regression issues on affected platforms. Change-Id: I2b766ccc9bf3eaae77b1dfc1a73e9acc2a88d8a9 Resolves: #89110 Releases: master, 9.5, 8.7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61642 Tested-by:
-
- Sep 20, 2019
-
-
Benjamin Franzke authored
Support for PSR-17 HTTP Message Factories has been added. PSR-17 HTTP Factories are intended to be used by PSR-15 request handlers in order to create PSR-7 compatible message objects. Classes may use dependency injection to use any of the available PSR-17 HTTP Factory interfaces. The Request/Response base class (Message) is adapted to be able to lazily initialize a stream when getBody() is called. This is done as the PSR (Stream)RequestFactoryInterface does not allow to control Stream properties. Therefore it is a performance optimization to defer initialization. It is likely, that a new Stream will be added to a Request with withStream() anyway. (Which would mean resources for the intermediate stream would have been wasted) Furthermore some DocBlocks are adapted to reflect the variadic UriInterface/StreamInterface parameters that are already handled in code but were not documented. These cases are needed/required by the PSR-17 factory implementation now. composer require psr/http-factory:^1.0 Releases: master Resolves: #89018 Change-Id: Ie6b9d865679bbf6f5d3d030b0ed1a3f277c47a3d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61558 Tested-by:
-
- Sep 13, 2019
-
-
Oliver Hader authored
When a record was modified in a workspace, and then discarded, TYPO3 previously set the t3ver_wsid to "0", which basically meant "we release it to live workspace as a offline version with pid=-1". However, this turns out to be ugly, as this information is then floating in live workspace, without any information where this record was from. Instead, "discarding versioned records" now keeps the t3ver_wsid=X, and just marks the versioned record as "deleted" - or removes it completely if the database table does not support to mark records as deleted. As a result, there will be no records in live workspace anymore with "pid=-1" in the future anymore. To remove any "old" discarded records, an upgrade wizard will follow in a followup patch. Resolves: #89166 Releases: master Change-Id: I8ccab3cd2053c27d9b0ecd9f171a83b9097f29dd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61671 Tested-by:
Daniel Gorges <daniel.gorges@b13.com> Tested-by:
-
Andreas Fernandez authored
The package phpdocumentor/reflection-docblock introduces major regressions starting with 4.3.2 that leads to getting nullable compound types (e.g. `?string|int`) parsed completely wrong, which currently also breaks in symfony/property-info. Also, it became stricter about type annotations which currently collides with Fluid. For this reason, the package is marked as conflicting starting with version 4.3.2. Resolves: #89167 Releases: master Change-Id: Ife9d14c01de5bea2179dafc572820f292039a202 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61702 Tested-by:
-
- Sep 11, 2019
-
-
Oliver Hader authored
* Clipboard now correctly resolves record localizations of a workspace * PageLayoutController new correctly determines sub-pages that are new in a particular workspace * SlugHelper & TypoScriptTemplateModuleController can be simplified by using WorkspaceRestriction directly * common function test scenario tree (based on YAML) is introduced for ext:backend in order to be used as structure for other tests * required testing framework changes support version and language variants and combination much better now Resolves: #89138 Releases: master Change-Id: Ia4b412d48dd3ea92adc60c729ad6feb27c22b812 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61663 Tested-by:
Achim Fritz <af@achimfritz.de>
-
- Sep 04, 2019
-
-
Susanne Moog authored
composer require typo3/testing-framework:"~5.0.12" Resolves: #89073 Releases: master Change-Id: If6384d11c0201cea760b384a8b7d7b361874e815 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61617 Tested-by:
-
- Aug 28, 2019
-
-
Andreas Fernandez authored
This patch updates friendsofphp/php-cs-fixer to version 2.15.2 and applies fixes to the code. Executed commands: composer require --dev "friendsofphp/php-cs-fixer:^2.15.2" ./bin/php-cs-fixer fix --config Build/.php_cs Resolves: #89031 Releases: master, 9.5 Change-Id: I3761ab56f66b6bd3b0fadc2bfa354cf4010b5e43 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61564 Tested-by:
-
- Aug 13, 2019
-
-
Andreas Fernandez authored
The bugfix for #88883 makes use of natural sorting via Symfony's Finder component. Since TYPO3 depends on version 4.1, this won't work since the feature was introdcuced in version 4.2. This patch updates symfony/finder to version 4.3. Executed composer command: composer require symfony/finder:^4.3 Resolves: #88953 Related: #88883 Releases: master Change-Id: Ia4c3b246153d763f640de3dc1deeed6b40c601f4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61491 Tested-by:
-
- Aug 05, 2019
-
-
Andreas Fernandez authored
This patch updates nikic/php-parser to version 4.2.2, which brings better support for PHP 7.3 and adds initial support for PHP 7.4. Changelog: https://raw.githubusercontent.com/nikic/PHP-Parser/v4.2.2/CHANGELOG.md Composer command: composer require nikic/php-parser:^4.2 Resolves: #88914 Releases: master, 9.5 Change-Id: I6d7feb8851be6e5565cb069fb33c279f916f4667 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61435 Tested-by:
-
- Jul 23, 2019
-
-
Oliver Hader authored
Change-Id: Ic8975554d38eef468af5454152a0200e21eb962d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61339 Tested-by:
-
- Jul 17, 2019
-
-
Benni Mack authored
Since Context API was introduced in TYPO3 v9, PageRepository is highly decoupled from $TSFE->sys_page, and fully works standalone. It is also used in various places where TSFE is not needed, or required, but also in places of EXT:core. Especially parts like RootlineUtility, which depends on PageRepository very much, cannot live without it. I propose to move this highly important PHP class into EXT:core, in order to allow to decouple EXT:frontend even further from EXT:core. The FQCN is moved from - \TYPO3\CMS\Frontend\Page\PageRepository to - TYPO3\CMS\Core\Domain\Repository\PageRepository It can be assumed to use PageRepository for any use-case and actually reduce usages towards BackendUtility::get... by using this API more and more. Further adaptions could be to reduce the logic within PageRepository and move this into QueryBuilder and assimilate especially the "versionOL" behavior. Resolves: #88746 Releases: master Change-Id: Id8225100ac60bd77fc7e1303efb4c46b741d3415 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61166 Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
-
- Jul 16, 2019
-
-
Benni Mack authored
The new PSR-14 standard for dispatching Events (that is: to extend a Framework without having to modify a frameworks' code) adds a EventDispatcher object that can dispatch Event objects to EventListeners. In PSR-14 every dispatched event is an object. It uses PHP class names as identifiers for events. Class hierarchies may be used to group events. A ListenerProvider object collects available listeners from an extension and allows to listen and/or modify data provided by the Event object. The current implementation relies on a custom TYPO3-specific ListenerProvider that is configured using Symfony's Dependency Injection tags. As an example the Mailer-postProcInitialization signal/slot is replaced by an Event. This first patch introduces the feature, and does not deprecate anything yet. The most important part is that new Events can use this API instead of Hooks in TYPO3 v10. Short-Term goal is to deprecate SignalSlot dispatcher in TYPO3 v10, and migrate all signals to the EventDispatcher. Resolves: #88770 Releases: master Change-Id: I3649ddb9b9340640199279e6af3c040bffc397fe Signed-off-by:
-
- Jul 13, 2019
-
-
Benni Mack authored
This patch re-arranges the TYPO3 Core internally used middlewares for lifting off the weight of $GLOBALS['TSFE'] as Site Handling already introduced a lot of functionality which can now be utilized further. For this reason, the Frontend Rendering chain has been adapted. * If there is a "Site" + "Language" resolved, this information can be used directly, as there are no dependencies currently. * Frontend + Backend User Authentication works regardless of TSFE, Frontend User is added to the Request object as attribute to be added to TSFE later-on. * Resolving the Page ("slug") and mapping them to Page Arguments (URL parts + GET parameters) as well as validation against cHash is fully decoupled from TSFE. After that, TSFE is instantiated, which now gets all resolved objects injected. TSFE now only resolves the rootline against the proper permissions (auth) and validates the final page. Once done, TypoScript is compiled / cached. TSFE still contains the rootline, TypoScript, and the information about which non-cacheables are there. RequestHandler creates or fetches cached content, but currently piped through TSFE. This should be simplified further later-on. Resolves: #88717 Releases: master Change-Id: I12807455fd8b01493b2da45cf73a5c532b108cbe Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61155 Tested-by:
-
