- Jun 21, 2019
-
-
Alexander Schnitzler authored
The BitSet class has been put into a DataStructure namespace although the core puts classes of these kind into a Type namespace. Therefore, the class has been moved. Releases: master Resolves: #88596 Change-Id: I18385a5c761e002f36bc33dcaeeb26ce7f6d187e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61098 Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Mathias Brodala <mbrodala@pagemachine.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Alexander Schnitzler <typo3@alexanderschnitzler.de>
-
Daniel Siepmann authored
As this is what its called. This also should make searches easier, as there is only one way to write it. Relates: #88600 Releases: master, 9.5 Change-Id: Ib6fcd4402b4a34aeaf0735a40788a18a324587dd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61103 Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Tom Warwick <tom.warwick@typo3.org> Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
Claus Due <claus@phpmind.net> Reviewed-by:
-
Helmut Hummel authored
By concept for frontend rendering the page title and meta tags are not meant to be stored in page cache in order to allow non cachable plugins to modify those. Currently both page title and meta tags are stored in separate cache entries, which violates the concept above and unnecessarily tightly couples those code parts to the TypoScriptFrontendController and internal logic of it. This patch removes these caches. In order to properly handle the uncached rendering state, we make sure the meta tag registry is properly serialized with all managers. Resolves: #88179 Releases: master, 9.5 Change-Id: If5200398bf9ab9db09ab97403c976d82cb33d01d Signed-off-by:
Frank Naegler <frank.naegler@typo3.org> Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60520 Tested-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
Richard Haeser <richard@maxserv.com> Reviewed-by:
-
Susanne Moog authored
Some tests still use hardcoded 'typo3temp' for creating files and folders. Where possible, this has been changed to use varPath from Environment class instead. Resolves: #88551 Releases: master Change-Id: I2d9a8edfb3fb33cc8f86f8e487603d0c72ef3ff0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60946 Tested-by:
-
Benni Mack authored
In preparation for our next maintenance release, symfony components are updated to their latest versions. Composer Command: composer update symfony/* --with-all-dependencies Resolves: #88595 Releases: master, 9.5 Change-Id: Ib380cbe7fec57488bf0ca10328486bc9c5fcbd5c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61096 Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
-
- Jun 19, 2019
-
-
Oliver Hader authored
With #88366 "cache_" prefix has been deprecated. However, when retrieving a deprecated cache like "cache_subject" its identifier gets transformed to just "subject" which is (probably) not available in cache configuration keys. That's why keys of cache configurations have to be transformed as well. Resolves: #88512 Releases: master Change-Id: I224d55e71011a437ed2e990d13b1edbee08770b7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60892 Tested-by:
-
Benni Mack authored
Profiling shows that when linking to 100 pages, SiteFinder (which instantiates SiteConfiguration) is instantiated 100 times. Although SiteFinder information might change during one request, the SiteConfiguration does not (except when updating the Configuration via API). So, a first-level-cache can be used to avoid calls to "cache_core" multiple times during one request, and SiteConfiguration can become a Singleton instance. Resolves: #88577 Releases: master, 9.5 Change-Id: I3d9167da9442d684d32a73d6cf2003c91bdf4d68 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61078 Tested-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
-
Devid Messner authored
Resolves: #87147 Releases: master, 9.5 Change-Id: Ia909104bc663d4191f21cb1bf0e25c0212388e2f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/59133 Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
-
Benni Mack authored
This change removes the "TCEforms" option when parsing FlexForms data in DataHandler, when dealing with FlexForms that contain sheets. This way, FlexForms RTE configuration is properly set and no double spacings for linebreaks are used. According to the issue, this only happened when fields specifically within sheets are configured, for fields without sheets, this has been working already. In order to ensure both cases are working, tests are applied for both variants. Resolves: #80778 Resolves: #81748 Releases: master, 9.5, 8.7 Change-Id: I38facfa9e1065d4730f895aa178a049c07c443f8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60902 Tested-by:
Jan Kornblum <jan.kornblum@gmx.de> Tested-by:
-
- Jun 18, 2019
-
-
Andreas Fernandez authored
All modules of the Install Tool used in modal windows now share a common abstract class that contains some boilerplate code required for most modules. Resolves: #88518 Releases: master Change-Id: I0c2f03f098c731e5a0c499ce91400c22a8c1f890 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60897 Tested-by:
Jonas Eberle <flightvision@googlemail.com> Tested-by:
Simon Gilli <typo3@gilbertsoft.org> Reviewed-by:
-
Susanne Moog authored
composer require --dev typo3/testing-framework:~5.0.10 Releases: master Resolves: #88580 Change-Id: I1dcef11cee0caa730463919146b3732d7838e683 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61081 Tested-by:
-
Manuel Selbach authored
doctrine/dbal 2.8.x ran into unmaintained mode: https://www.doctrine-project.org/projects/dbal.html We should upgrade to at least 2.9: composer req doctrine/dbal:^2.9 Resolves: #88579 Releases: master Change-Id: I18962bd313018abec8e52bada6df9aca6aa4143f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61080 Tested-by:
Susanne Moog <look@susi.dev> Reviewed-by:
-
Sybille Peters authored
Resolves: #88578 Releases: master, 9.5 Change-Id: I5fc57a9c61d5f02838f3afd3c305ae0b7b037dfc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61079 Tested-by:
Joerg Kummer <typo3@enobe.de> Reviewed-by:
-
Benjamin Franzke authored
As it produced a warning: 1) TYPO3\CMS\Frontend\Tests\Unit\DataProcessing\SiteProcessorTest:: nullIsProvidedIfSiteCouldNotBeRetrieved Trying to configure method "getSiteFinder" which cannot be configured because it does not exist, has not been specified, is final, or is static Resolves: #88576 Related: #88568 Releases: master Change-Id: Icf72100282ce24c87b6bb9f49fc978b6187a817e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61074 Tested-by:
-
- Jun 17, 2019
-
-
Jonas Eberle authored
Rephrases button title and success message for user preference reset. Resolves: #88520 Releases: master, 9.5 Change-Id: Ib2d3180a417366249df8fa9c1faa47c74cca022a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61040 Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Reviewed-by:
-
Manuel Selbach authored
doctrine/dbal 2.8.x ran into unmaintained mode: https://www.doctrine-project.org/projects/dbal.html We should upgrade to at least 2.9: composer req doctrine/dbal:^2.8.1 which installs 2.9.2 Resolves: #88553 Releases: master, 9.5 Change-Id: Id0c20cbb3102b5086e1c4d9dcef1b32fed67db7d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60994 Tested-by:
Manuel Selbach <manuel_selbach@yahoo.de> Reviewed-by:
-
Benni Mack authored
Locales resolves the user-defined TYPO3-languages and its dependencies via TYPO3_CONF_VARS, which are only finally available when all extensions' ext_localconf.php is included. For this reason, Locales::initialize() can be deprecated and moved into the regular constructor, but then the Bootstrap should not do the initialization anymore, which happens at the point now, when Locales first gets initialized (which happens in Frontend within TSFE and PageRenderer and in Backend within $LANG). For this reason, it is removed from Bootstrap, where it was first placed in TYPO3 4.6 when no proper bootstrap set up was given. Resolves: #88569 Releases: master Change-Id: Ife2e248412c1b206abffcdd21df0d01e44834cea Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61046 Tested-by:
-
Benni Mack authored
SiteMatcher is a container around SiteFinder now as PseudoSite handling was removed, so SiteFinder can be used directly. Resolves: #88568 Releases: master Change-Id: Ib0f5a42351ed5c11c25458b74074b80f5c574bbd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61043 Tested-by:
-
Alexander Schnitzler authored
This patch removes the automatical registration of two types of validators. - model validators - type validators Model validators are those validators that follow a specific namespace and class naming derived from domain models. Given a model \Vendor\Extension\Domain\Model\Foo, extbase searched for a valiator \Vendor\Extension\Domain\Validator\FooValidator. If it existed, it had been registered automatically and could not be disabled at all. Type validators are similiar to model validators. Given a non model action parameter or model property like int, string, float, DateTime and such, extbase searched for validators in the namespace TYPO3\CMS\Extbase\Validation\Validator. There is a TYPO3\CMS\Extbase\Validation\Validator\StringValidator for example which had been registered for string type params and properties. Said validators could not be disabled at all. There are several reasons why the automatic registration has been removed: - First of all, this behaviour led to an unknown amount of actual registered validators. Developers that are new or simply not familiar with the concept of validation magic could easily become frustrated. - Then there is the problem that validation takes place, no matter if it was needed or wanted. A domain validator, which looked quite handy in the first place, had to be reduced to the validation logic that would fit all cases where according objects had been passed into methods. No matter the context. The context however matters a lot. One might want to have different validation rules depending on if objects are created, updated or deleted. This distinction was impossible and therefore model validators could be a burden. - Last but not least, the automatic registration is a problem when introducing validation groups. Validation groups cover the context aspect mentioned earlier. By grouping validations one can create and register different validators and apply them given by contexts like create, update, delete and such. Releases: master Resolves: #87957 Change-Id: If8f590a1bedb428c8884cd61828d8cc671ee92e1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60298 Tested-by:
Stefan Froemken <froemken@gmail.com> Tested-by:
-
Susanne Moog authored
Some unit tests still have problems on Windows. - setlocale will not error even if the locale is not found - file permissions don't work the same as the unix style version - absolute paths do not start with a slash - files from finder may contain mixed slashes - generating different hash values when used as key Tests have either been adjusted to accomodate the differing behaviour or skipped if appropriate. Resolves: #88552 Releases: master Change-Id: I32344c2a0a0797db087a3ccad45d3b626715ab77 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60945 Tested-by:
Benjamin Kott <benjamin.kott@outlook.com> Tested-by:
-
Benni Mack authored
When parsing TypoScript, PageTSconfig and UserTSconfig is taking into account for evaluting if "TSFE.constants" is set in PageTSconfig. If this is used, this acts as a default constant. However, this feature has various drawbacks, and has been superseded by actually having constants globally (FE/BE) and via Conditions available. For frontend calls with empty pagesection caches, this improves performance greatly, especially in pages on a deeper level (recursion). This also reduces the footprint to have the TypoScriptParser (incl. condition matching) being called too often. Resolves: #88564 Releases: master Change-Id: Icbdfa9918a9a79510a87198bf033c4de96d71107 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61034 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
-
- Jun 14, 2019
-
-
Georg Ringer authored
The following methods of `\TYPO3\CMS\Core\Utility\VersionNumberUtility` are unused and can be deprecated: - `splitVersionRange` - `raiseVersionNumber` - `convertIntegerToVersionNumber` Resolves: #88554 Releases: master Change-Id: I28378a39d7cae4d2ae09cfb6a85c5d294565a2f7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60997 Tested-by:
-
Benni Mack authored
There are a lot of places where AbstractUserAuthentication and the dependents (BE/FE user auth) set various settings, both in the constructor and the start() method. All possible settings are now moved to the constructor, or to dependent properties in subclasses. Some changes are now in place: - UserAuth->loginType must be set now (which was previously in start()). This is now checked in the constructor. - Most of the variables (sessionTimeout/sessionDateLifetime) are now set and evaluated inside the constructor, making start() much simpler to understand and read. Resolves: #88527 Releases: master Change-Id: Ie03b8b93f869f5bafae8f660d6c983bec308f2fa Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60875 Reviewed-by:
-
Andreas Fernandez authored
Resolves: #88262 Resolves: #85346 Releases: master, 9.5 Change-Id: Ia72ef1b670841d90ec0251c99b7f4d3dc1e7770a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60900 Tested-by:
Riccardo De Contardi <erredeco@gmail.com> Tested-by:
Sven Juergens <typo3@blue-side.de> Tested-by:
-
Benni Mack authored
Introduced with https://review.typo3.org/c/Packages/TYPO3.CMS/+/60895 cHash's that are used within the URL but not needed anymore, should rather create a redirect instead of silently unsetting the cHash argument. Related: #41033 Resolves: #88531 Releases: master, 9.5 Change-Id: Iaae3e72160c055f8848942d506f7cc3e25d31af4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60905 Tested-by:
Nicole Cordes <typo3@cordes.co> Tested-by:
-
- Jun 13, 2019
-
-
Benni Mack authored
The two TypoScript options * config.htmlTag_langKey * config.htmlTag_dir have been removed, as they have no effect anymore in TYPO3 v10, which only works with Site Handling. Site Handlings "direction" and "twoLetterIsoCode" are already in place and used when Site Handling is active. Resolves: #88560 Releases: master Change-Id: I8ef2a8b8ccd9c790fd7db940e908e8a362ec4ca3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61003 Tested-by:
-
Benni Mack authored
Various documentation in TSFE is updated, in addition to having $TSFE->setAbsRefPrefix() to be set within the postProcessing to overcome issues when the call is forgotten in custom TSFE instances. Resolves: #88555 Releases: master Change-Id: Ib3ce22db1e6ce7b0985d486d584c26f25755efa4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60998 Tested-by:
-
Dmytro Nozdrin authored
Conditions with `tree.rootLineIds` if matched caused page cache regeneration on each request. Resolves: #88374 Releases: master, 9.5 Change-Id: I5a9a2a429a80575b654a6894a3515c8ca8ec8db4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60771 Tested-by:
-
Benni Mack authored
For further TSFE-related changes, the frontend request workflow now stores user-/session-related information in the middleware. This is a first step in order to reduce the dependencies of TSFE + FrontendUserAuthentication. This patch is breaking as certain hooks (like EOFE) do not have session data stored anymore. Related: #88540 Resolves: #88541 Releases: master Change-Id: I1e9a66b759d6edfd4c0e5a8ede02aa7a73b65b0f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60939 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
-
Benni Mack authored
The only occurrence for 'loginSecurityLevel' checks for empty and falls back to 'normal' (also defined in #81852 this must be set to normal). Single usage in AbstractUserAuthentication: trim($GLOBALS['TYPO3_CONF_VARS'][$this->loginType]['loginSecurityLevel']) ?: 'normal'; Instead of having this set to "factory configuration", (= writing to LocalConfiguration.php on new installation), this can be set to 'normal' in DefaultConfiguration directly. EXT:rsaauth can be configured to set this to "rsa" in an instance with RSA enabled (and has already done so before). The main benefit is that this option (if set to "normal") can be removed from LocalConfiguration if set to "normal" as it is then taken from DefaultConfiguration.php Resolves: #88549 Releases: master Change-Id: I2f8c088230b334a03c5acf9d09721dd42e67c059 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60972 Tested-by:
-
- Jun 12, 2019
-
-
Gianluigi Martino authored
Add title to the two topbar buttons on the left: - Minimize/maximize module menu - Collapse page tree Resolves: #88385 Releases: master, 9.5 Change-Id: I9641bdf5454f1f50e6c4ab67c96f663b8b5d8c73 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60862 Tested-by:
Sybille Peters <sypets@gmx.de> Tested-by:
-
Benni Mack authored
Extensions should make use of TYPO3's native functionality for using FAL-based folders, or the Environment API and TYPO3's File APIs to create folders when needed. The ext_emconf.php option "createDirs" option is removed, and not evaluted anymore. The public method `ensureConfiguredDirectoriesExist` in FileHandling Utility is removed, however the class is marked as internal. This change is a pre-work for the CLI Initiative where there are currently workarounds in using this functionality for "activating" an extension. Resolves: #88525 Releases: master Change-Id: I52ec31da541d3740977068981944bd5a1dd0d2f7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60485 Tested-by:
-
Benni Mack authored
With the introduction of CKEditor in TYPO3 v8, the support for images in RTEs is dropped, however functionality was kept for compatibility with RTEHtmlArea, which was still available in TYPO3 v8 as separate extension. The functionality to handle images in CKEditor is possible to be applied again, however, as this cannot be managed properly via FAL in its current state, the previous functionality is remvoed from Core. Separate CKEditor extensions as already published, are able to manage the image handling in CKEditor directly already. Dropped * setting TYPO3_CONF_VARS[BE][RTE_imageStorageDir] * transformation setting "ts_images". * softref "images" logic * ImportExport->getRTEoriginalFilename() * RteHtmlParser->TS_images_rte() * CLI Command: cleanup:rteimages and Class RteImagesCommand Resolves: #88500 Releases: master Change-Id: Ie564b19a7d0f9b7d46398094c8d7ecd845e31a65 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60886 Tested-by:
Daniel Gorges <daniel.gorges@b13.de> Tested-by:
-
Jonas Eberle authored
Fix two issues in the extension configuration tool if more than one extension is using the same configuration key: * Remove duplicate HTML IDs in extension configuration tool * Correctly add hidden fields with value=0 for checkboxes within every sub-<form>, not only on first occurence (first extension) of any given configuration key Resolves: #88426 Releases: master, 9.5 Change-Id: Ifbdb3b495443aa5521a4b5265ae3c29c2bc222b8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60831 Tested-by:
Guido Schmechel <guido.schmechel@brandung.de> Tested-by:
-
- Jun 11, 2019
-
-
Anja Leichsenring authored
Switching from accessibleMock to prophecy resolves a lot of failures. Also, using a concrete instance instead accessibleMockForAbstractClass reduces issues. Resolves: #88530 Releases: master, 9.5 Change-Id: I102597f74a98443fe139a76b8f168abf61349e3d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60903 Tested-by:
-
- Jun 10, 2019
-
-
Stephan Großberndt authored
Releases: master Resolves: #88535 Change-Id: Ibeb645965840c8c4e78f5e4d13272db32e9fc308 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60933 Tested-by:
-
- Jun 09, 2019
-
-
Andreas Fernandez authored
If a backend usergroup has no permission to edit page properties, the wizard for content element creation is not rendered properly. This is due to a missing import of the `PageActions` module. This patch now always loads the module and makes its callback depending on proper permissions. Resolves: #88532 Related: #87687 Releases: master, 9.5 Change-Id: Ie3acaf8fbf9bdeee425eae4b4d35cb2eb80b4d1d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60907 Tested-by:
-
- Jun 08, 2019
-
-
Benni Mack authored
If a cHash GET parameter is given, but there are no GET parameters that are relevant, a hash_calc() call against an empty string is done. However, the change now allows an invalid cHash if no check is necessary. This could happen when upgrading from older instances where a cHash is not needed anymore. Bots would not then fill up the error log but get the new page (with a valid 200 result) Resolves: #41033 Releases: master, 9.5 Change-Id: Id02701fcbece371a6b9ce0f92fe0be55dd972325 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60895 Tested-by:
-
Benni Mack authored
This patch removes unused variables: $GLOBALS['TYPO3_MISC']['microtime_BE_USER_start'] $GLOBALS['TYPO3_MISC']['microtime_BE_USER_end'] $GLOBALS['TYPO3_MISC']['microtime_end'] $GLOBALS['TYPO3_MISC']['microtime_start'] are replaced by properly using - TimeTracker->start() - TimeTracker->finish() (new method) to encapsulate the logic into the main method. Resolves: #88498 Releases: master Change-Id: I158e4b3aed002f688f117488cb0300c6523e791f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60769 Tested-by:
-
- Jun 07, 2019
-
-
Andreas Fernandez authored
With #88459, the closing tag `</property>` was accidentally not removed, leaving a broken XML structure. This patch removes the closing tag. Resolves: #88526 Related: #88459 Releases: master Change-Id: Iee6ca5f11f12d3f84f5bc0ef4afeefcb3b37bf73 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60901 Tested-by:
-
