- 13 Jan, 2022 1 commit
-
-
This change introduces a new PSR-14 event for manipulating menu items in a menu. The hook $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['cms/tslib/class.tslib_menu.php']['filterMenuPages'] is removed, and AbstractMenuFilterPagesHookInterface deprecated. Resolves: #92508 Releases: main Change-Id: I2960e5021b2ba49e1b26e68f2bb0cbed809d60a7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72955 Tested-by:
Oliver Bartsch <bo@cedev.de>
Tested-by: 
core-ci <typo3@b13.com>
Tested-by: Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 12 Jan, 2022 2 commits
-
-
Using inline JavaScript when initializing RequireJS modules in individual dashboard widgets has been deprecated. Widget implementations have to be adjusted accordingly. Basically `RequireJsModuleInterface` has to be replaced by `JavaScriptInterface` relying on `JavaScriptModuleInstruction`. Resolves: #96524 Releases: main Change-Id: I5eb74aa54aef6d4f3a9419aaa7e2d391d98ce408 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73002 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
Reviewed-by: -
Global constants TYPO3_version and TYPO3_branch have been deprecated with introduction of class \TYPO3\CMS\Core\Information\Typo3Version in v9.5.15 and are removed together with some last usages. Resolves: #96523 Related: #96107 Releases: main Change-Id: I0fd90a9f913d83a555a9744117f76d63468a1048 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73000 Tested-by:
Oliver Bartsch <bo@cedev.de>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 11 Jan, 2022 1 commit
-
-
Benni Mack authored
The method cObj->getMailTo() is only used in EmailLinkBuilder and its functionality is now moved into this class, as the scope belongs to this class. Resolves: #96500 Releases: main Change-Id: Id051a5889997be7a2115a2a68e223797b5a6431c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72944 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: Stefan Bürk <stefan@buerk.tech> Tested-by:
Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 08 Jan, 2022 1 commit
-
-
The type can already be inferred from the source code. The cleanup was run automatically with a PHPStorm plugin. Resolves: #96482 Releases: main Change-Id: I669145adc66dc898f3016de1958cf0105c988243 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72907 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <bfr@qbus.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
-
- 30 Dec, 2021 2 commits
-
-
Benni Mack authored
This change enables raises Symfony's minimum version to 5.4.0 as this is a LTS version. Resolves: #96171 Releases: main, 11.5 Change-Id: Ia2acbe0bca60e0dbdb96cb2fe2e82a63f9575554 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72434 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
-
This is a preparatory update to help migration to ES2020 modules ("ESM"). TypeScript >=4.1.1 fixes it's es2020 module target to allow import.meta, see https://github.com/microsoft/TypeScript/issues/41249 Also related eslint tools are updated and the configuration format is streamlined to json, while we are at it. (not really needed, just drive-by cleanups) Notes: * @types/chrome is removed because of a conflict. It has been added in #82595 but it has actually never been used. This package contains a dependency to @types/filesystem which is currently not TypeScript 4.5 compatible, therefore both packages are removed. * tsconfig.json is adapted to explicitly configure "useDefineForClassFields": false. With our current target ES2017 this defaults to false, but with TypeScript >=4.3 and target ES2020 the default changes to `true`. Lit requires this setting to be false for decorators to work, so we add explicit configuration as recommended by Lit: https://lit.dev/docs/components/decorators/#decorators-typescript * The `true` ("force-reload") parameter of document.location.reload() calls is removed as this flag is non standard an only available in firefox. It is not longer permitted by TypeScript 4.5, also see: https://developer.mozilla.org/en-US/docs/Web/API/Location/reload#location.reload_has_no_parameter * Many compiled files are changed because calls like `foo.bar()` (where `foo` is imported from another module) are now transpiled to `(0, foo).bar()` in order to avoid calling module exports with a `this` value: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-4.html#more-compliant-indirect-calls-for-imported-functions This is to comply with native ES6 Modules and therefore marked as a breaking change in TypeScript, but it only affects names imports and therefore doesn't affect the instances we export via `import =`. (It only affects imports from jquery, moment, lit and function exports) This actually brings us closer to ES6 module compatibility. Commands executed: # Introduces in #82595 and unused since then yarn remove @types/chrome yarn add --dev \ typescript@~4.5.0 \ grunt-eslint@^24.0.0 \ eslint@^8.0.1 \ @typescript-eslint/eslint-plugin@^5.8.0 \ @typescript-eslint/parser@^5.8.0 \ @typescript-eslint/typescript-estree@^5.8.0 yarn build Releases: main Resolves: #96436 Related: #96323 Change-Id: Ia5a7e0408af906ff889e7e9435f7868fb3d0ac34 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72806 Tested-by:core-ci <typo3@b13.com>
Tested-by:
-
- 21 Dec, 2021 3 commits
-
-
Christian Kuhn authored
To stick to best practice, the patch adapts all f:uri.resource ViewHelper usages to "EXT:" syntax. Resolves: #96423 Related: #96414 Releases: main Change-Id: Icba87d954f939a42ca59fbe78e7c932f0228f11e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72766 Tested-by:
core-ci <typo3@b13.com>
Tested-by: 
Simon Gilli <typo3@gilbertsoft.org>
Tested-by: Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Simon Gilli <typo3@gilbertsoft.org>
Reviewed-by: -
Releases: main Resolves: #96228 Change-Id: I680bf20c1a3dc63003cf1638ec680ca6ab07447f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72492 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Susanne Moog <look@susi.dev> Tested-by:
-
The core version service now uses the new entry point of the REST API available via https://get.typo3.org/api. The old entry point is still available but should not be longer used. For more information see `https://get.typo3.org/api/doc <https://get.typo3.org/api/doc>`_ and `https://github.com/TYPO3/get.typo3.org/pull/272 <https://github.com/TYPO3/get.typo3.org/pull/272>`_. Resolves: #92020 Releases: main, 11.5, 10.4 Change-Id: I2c92554e9ba212827b6412d4a88ac5c92e26aa17 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65342 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 20 Dec, 2021 2 commits
-
-
Christian Kuhn authored
The patch makes the bulk of ViewHelper classes more strict and applies some general love. Some ViewHelpers have been left, those will see bigger refactorings soon. All affected classes are final, the changes are (hopefully) non-breaking. * declare(strict_types=1) if missing. * Use self:: instead of static:: since all VH's are final, so there is not point in using late static binding. * Return and argument type hints where possible and reduction of methods doc annotations which are covered by PHP method signatures. * Add types to some class properties. * Protect some detail methods that were apparently public by accident. This is not considered breaking. * Avoid extbase LocalizationUtility::translate() in favor of core LanguageService. * Avoid static class state, especially with TSFE. * Minor comment fixes. Change-Id: I4e3b9d01ea92802e47d05a10f4243196120b8510 Resolves: #96400 Related: #96368 Releases: main Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72741 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Resolves: #96392 Related: #95320 Releases: main Change-Id: I6dfe1e5ea95c1e5ceb748e2b1c50eec8644f1ecf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72732 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 17 Dec, 2021 1 commit
-
-
Christian Kuhn authored
As anticipated in v11 with #95298, this patch declares ViewHelper classes PHP final, third party extensions can no longer extend core ViewHelpers. There is one exception: The ext:fluid FormViewHelper, which is currently extended by ext:form. This can't be resolved easily since it's on one hand quite a bit of code that would have to be copied, and more importantly, the FormField* ViewHelpers refer to the "parent" FormViewHelper class name in various places. Declaring FormViewHelper final thus needs a different refactoring, which may be done in v12 with further patches. Resolves: #96368 Related: #95298 Releases: main Change-Id: I7e8a587dadef4e411390710dd47e309cd2414e65 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72671 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 15 Dec, 2021 1 commit
-
-
The routes added via ExtensionManagementUtility::addModule() are missing when the UriBuilder/Router is used prior to ext_localconf loading. Also for this particular case, multiple instances of the Router class were created, as UriBuilder is loaded from the failsafe installtool container instead of using an instance from the symfony container (as created by LateBootService n loadExtLocalconfDatabaseAndExtTables). This resulted in multiple routers being loaded with different sets of routes. This patch ensures that the routes are loaded from a UriBuilder/Router instance that is fully populated with information from ext_localconf. Therefore GeneralUtility::makeInstance() is avoided and UriBuilder is fetched from the late booted container instead. Resolves: #95806 Releases: main, 11.5 Change-Id: Id57bf09fb7798eac26dbdbc6ed89228c54fbafb9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72463 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 14 Dec, 2021 2 commits
-
-
Benni Mack authored
The method TemplateService->updateRootlineData() can be removed. Until TYPO3 v11 TemplateService resolved the TypoScript for a specific page, then found out the actual used language (config.sys_language_uid via TSFE->settingLanguage()) and then fetched the (translated) rootline based on the resolved language information. This is not needed anymore, as settingLanguage() does not call this method anymore, and is called much earlier now, see https://review.typo3.org/c/Packages/TYPO3.CMS/+/65044. TypoScript is now always loaded after a translated page rootline has been fetched. This method is now completely unneeded, and is remoevd without replacement as the concept has now been streamlined. Resolves: #96351 Related: #23736 Releases: main Change-Id: If959a36333fcf5c91bee84ee497fddd2bfcec89b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72605 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: -
Benjamin Franzke authored
Some modules are missing jquery imports. This currently works as jquery is exposed in the global object (window.$ and window.jQuery) and likely loaded by some other module. Still, loading may fail when jquery hasn't been loaded by another module, therefore these occurences are fixed and the type declarations are patched to avoid marking jquery available as global object (therefore typescript will complain when using jQuery or $ without importing it). Releases: main Resolves: #96349 Related: #96323 Change-Id: I7f57137a1f23416aa90579de8a1860a42a7a6d46 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72646 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 13 Dec, 2021 4 commits
-
-
Oliver Bartsch authoredContextMenu item providers are now automatically tagged and registered, based on the implemented `ProviderInterface`, using the auto configuration feature from the DI container. The registration via `$GLOBALS['TYPO3_CONF_VARS']['BE']['ContextMenu']['ItemProviders']` has been removed. To enable the auto configuration, the context information (table, record identifier, context) is no longer passed as constructor argument, but instead using the new `setContext()` method. This is done in the `ContextMenu` class, prior to any other action, e.g. `canHandle()`. In case extensions with custom item providers extend the AbstractProvider, while not overwriting the constructor, nothing has to be changed. Only the registration via global TYPO3 configuration should be removed. Resolves: #96333 Releases: main Change-Id: I7e65102163d5cb6129ed2e8bd13c10660871811c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72627 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: Oliver Bartsch <bo@cedev.de> -
Deprecates BackendUtility::getUpdateSignalCode as well as using custom singal callbacks providing `JScode` containing inline JavaScript. Resolves: #96136 Releases: main Change-Id: I1462625ac3aee2a71da3956f79a6ffde6d620be5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72373 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
This fix a warning when you click on "SMTP Settings" in "Configuration preset". Resolves: #96348 Releases: main, 11.5 Change-Id: Ic6ec6b7efd9dde2f7c365fa391e6c358192dc23b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72644 Reviewed-by:
Oliver Bartsch <bo@cedev.de>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de> -
Benjamin Franzke authored
ECMAScript 2020 (ES11) introduced dynamic imports. TypeScript offers automatic type checking and resolution for the dynamic import syntax (when using static strings) and is able to transpile to require() calls in AMD output mode. Therefore all occurences where a require() is used directly, are migrated to the import syntax. Notes: * This change has a slight drawback: the generated code is slighter in order to add runtime detections for ES6 vs AMD style default. Although, this only applies in TypeScript AMD mode and will be compensated once switching to native ES6 modules. * top.require() calls are left as-is for now, as this cases can't be changed to top.import(): Property 'import' does not exist on type 'Window' Also something isn't available in native ES11 imports: TypeError: top.import is not a function We'll rather need a messaging api between the frames that allows to load top-level modules via import() in future. Resolves: #96326 Related: #96323 Releases: main Change-Id: Ia389da64255fb1fee76a4fbb0d2abdfc277921e1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72619 Tested-by:core-ci <typo3@b13.com>
Tested-by: 
Jochen <rothjochen@gmail.com>
Tested-by: Jochen <rothjochen@gmail.com>
Reviewed-by:
-
- 09 Dec, 2021 3 commits
-
-
Calling \TYPO3\CMS\Extbase\Utility::configurePlugin(), \TYPO3\CMS\Extbase\Utility::registerPlugin() and \TYPO3\CMS\Extbase\Utility::registerModule() with first parameter $extensionName containing a vendor prefix like 'Vendor.ExtensionName' is deprecated since version 10 and will now fail. Controller classes must be registered with their fully qualified name. The vendor prefix must be ommitted. It's possible to simplify and streamline extbase bootstrap and request handling a bit more. This will continue with other patches. Releases: main Resolves: #96047 Related: #87550 Change-Id: If98f2f5a048fd9e62373490c23ee5b117ffd2534 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66219 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: -
Christian Kuhn authored
This patch removes a series of unit tests from the test sets that are often either skipped or flaky. * There is little point in testing chmod() / chgrp() operations of low-level methods. That's a system thing we shouldn't test in detail. * Some tests have been marked as "i'm mocking too much, make me a functional test". Most of these are oooold. Don't read it, delete it. * Some phpunit @requires annotations have been broken since introduction and always resulted in "skip test". Remove those. Change-Id: I82e04613c9b72712e279d0819ada8e073658968d Resolves: #96301 Releases: main, 11.5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72567 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Benni Mack authored
The database abstraction layer Doctrine/DBAL 3.2 is now used throughout TYPO3 Core. Some class names have changed, the original Doctrine\DBAL\Result interface is now an object which is used in TYPO3 Core. Our internal drivers are now wrappers around PDOStatement instead of extending PDO's internal APIs. > composer req "doctrine/dbal:^3.2" -W Resolves: #96287 Releases: main Change-Id: I817dbcddf6406e44c94abcd25b3eb805032aec68 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72372 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 08 Dec, 2021 3 commits
-
-
In favour of allowing content-security-policy headers, inline JavaScript invocation via `AbstractControl::setOnClick` is now removed. Resolves: #96296 Related: #91814 Releases: main Change-Id: Ie8f6ea3911ab682c9f4be0590b4f4183ef656135 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72563 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
The extTablesPostProcessing hook was migrated to a PSR-14 event and is therefore now removed. Resolves: #96280 Related: #95065 Releases: main Change-Id: Ic4f472637e6cd026d4d75312e00a59848fac2b76 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72550 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Helmut Hummel <typo3@helhum.io> Tested-by:
-
Benni Mack authored
This change adds the new createSchemaManager() to our Doctrine DBAL Connection subclass to make it forward-compatible with Doctrine DBAL 3.x. createSchemaManager() is introduced with DBAL 3.x and is replacing getSchemaManager() which will be removed in Doctrine DBAL 4. Since this is a very lowlevel change, the method can be added without most notice for extension authors. Resolves: #96286 Releases: main, 11.5 Change-Id: Ifdccc2b0dff443bfe38d23a1bd1333b5c7c5db40 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72551 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 07 Dec, 2021 6 commits
-
-
Resolves: #96279 Related: #89555 Related: #87498 Related: #87499 Related: #88129 Related: #84262 Change-Id: I3030df36d82fa30c12f9c5752abe2be830d5b2b3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72549 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
This change introduces method param type declerations and enforces the caller to define at least two constraints to form a logical conjunction. In consequence, calling those methods with just one argument fails. Also, using an array of constraints as single argument fails. Releases: main Resolves: #96044 Change-Id: Ic6e9445d6d71ba979a42aed76d4a5de74489a614 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72244 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: -
Christian Kuhn authored
The install tool has a ext:report entry to check for old "joh316" password, which was a default back in very old times. This check has been marked as to-be-removed for v10 already. Resolves: #96274 Related: #85796 Releases: main Change-Id: Ic8b4a4aabfdb52b6560c57edeb477c1ba0a4de74 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72545 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
With #89738, a polyfill for jQuery promises was introduced to ease the migration to the introduced AjaxRequest API, included with TYPO3 v10. After two major versions, this polyfill may be removed. Some remaining occurrences are adjusted as well. Resolves: #96263 Related: #89738 Releases: main Change-Id: I31c812f1277c32f9f4b487fa78de85323209ac5b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72527 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Benni Mack authored
The past changes of migrating to Doctrine DBAL 3.x had some flaws: * Not all changes from Doctrine DBAL 3.x was applied * core relies on various invalid interfaces and classes, so the return types were wrong (also Tests used the old Statement class) * No explicit ->execute() and ->iterateAssociative() calls and fetchColumn() vs. fetchOne() * added executeQuery() and executeStatement() to QueryBuilder decorator class This change adapts most places to help in migrating to Doctrine DBAL 3.x for TYPO3 v12, but also avoids some unneeded deprecations for now. Resolves: #96247 Releases: main, 11.5 Change-Id: I60e99511efc4f9ec6d8d651c63becff028de4cf2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72478 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Oliver Bartsch authored
In favour of the LanguageServiceFactory, the container entry as well as the corresponding factory methods in LanguageService are now removed. Resolves: #96268 Related: #94414 Releases: main Change-Id: I355e8ba76f4d9594c478c37f16425d6da200048d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72538 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: Oliver Bartsch <bo@cedev.de>
-
- 06 Dec, 2021 3 commits
-
-
The install tool uses the FailsafeContainer for the DI. The $GLOBALS array did not contain the FAL drivers that were registered via the DriverRegistry API. The DriverRegistry is therefore now retrieved from the late-booted symfony container. Resolves: #93249 Releases: main, 11.5 Change-Id: Ic74eb22172e8e3d0ab0378a5b8dd52a0d82c9bd3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67444 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Previously deprecated methods getLanguageMode() and setLanguageMode() from Typo3QuerySettings are now removed. Resolves: #96258 Related: #89938 Releases: main Change-Id: I57bd5a2a77264edbdffe582477b7871b213a9fac Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72522 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
This removes the previously deprecated hook `t3lib/class.t3lib_parsehtml_proc.php:transformation`, which became useless due to removal of internal functionality in RteHtmlParser. Resolves: #96257 Related: #92992 Releases: main Change-Id: I8a6daf67f60e18646d608c06abefa1057be32708 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72521 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 05 Dec, 2021 4 commits
-
-
Christian Kuhn authored
Resolves: #96250 Related: #94957 Releases: main Change-Id: I8db4e93fb9627687b67f0294fab9d86ef0f46d61 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72515 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Christian Kuhn authored
Resolves: #96249 Related: #94958 Releases: main Change-Id: I10779f3c384dc6348b985edf72790020678e23cc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72514 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Christian Kuhn authored
Resolves: #96251 Related: #93726 Related: #94173 Releases: main Change-Id: I0ce15cc95c214e2a0c027dd913b446df7689e540 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72516 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Most deprecated code within authentication related classes, a last place will have a dedicated patch. Resolves: #96248 Related: #93023 Related: #95320 Releases: master Change-Id: I482a3dcd3c31c8625993ebff883b8b557e8967ed Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72476 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 04 Dec, 2021 1 commit
-
-
* TYPO3\CMS\Extbase\Mvc\Request->getBaseUri() * TYPO3\CMS\Extbase\Mvc\Request->getRequestUri() * TYPO3\CMS\Extbase\Mvc\Exception\InvalidRequestMethodException * TYPO3\CMS\Extbase\Mvc\Web\ReferringRequest Resolves: #96246 Related: #94367 Related: #94231 Related: #94228 Related: #94223 Releases: main Change-Id: I3d8019ba2a4535d2886f6876feba123d005f9964 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72512 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
