- 22 Nov, 2021 1 commit
-
-
TCA slug field generator option 'prefixParentPageSlug' has been added to be used for page records only. Slug generation for non-page records with pid=0 has been fixed with #94655 which introduced a endless loop if 'prefixParentPageSlug' is used as slug field generator option for record tables. This patch only process 'prefixParentPageSlug' for page records, thus ignoring it for non-page records and avoiding the endlees loop and as such prevent segmentation faults or memory_limit fatal errors. Resolves: #95485 Related: #94655 Releases: master, 11.5, 10.4 Change-Id: I20e1ac68bad6ad9447b03debbedb646495045ac3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72257 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
- 19 Nov, 2021 3 commits
-
-
Releases: master, 11.5, 10.4 Resolves: #96040 Change-Id: Idc83eedacc1ab00f761e179e394e173a071b6b0d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72130 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Benjamin Franzke authored
This applies to rendering of database mounts (from groups or from workspaces): They are now shown as children of the virtual root page (uid=0) as it used to be in TYPO3 v8. This is to allow workspace users to get an overview of all changes of all mounts by navigating to the virtual page uid=0. Releases: master, 11.5, 10.4 Resolves: #95854 Related: #95972 Related: #91145 Change-Id: I7f6370f327711396193cf56b63f15876350c2559 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72078 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
-
The example for the CommaSeparatedValueProcessor was missing a value for the fieldEnclosure property. This might lead to the assumption that this property can be "unset", which is not the case as it always defaults to a quotation mark ("). This is now fixed by adding an example value. Resolves: #93190 Releases: master Change-Id: If4ee5f358f71d83d0117cf0e9c2e07c619966b9f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72122 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 17 Nov, 2021 3 commits
-
-
docker on mac and windows WSL2 encapsulate a VM into the system. The current xdebug remote config does not work in those cases since the host IP can not be determined with the current solution. Switching to host.docker.internal works for macOS and WSL2, and works for linux too in combination with an extra_hosts setting. This requires linux to use at least docker 20.10, which shouldn't be a huge issue with casual developer machines. Resolves: #95999 Resolves: #94932 Releases: master, 10.4 Change-Id: I02acfeefc08f338841b4fecdb952c7da37ff65e1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72218 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Christian Kuhn authored
Switching to 20.10 gives us a feature we need in runTests.sh. Resolves: #96013 Related: #94932 Related: #95999 Releases: master, 10.4 Change-Id: I7eef83c130b76cab84dff7d595b7807d34b22ce7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72213 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
The identifier from the linkHandler page TSconfig was formerly used as the reference table name "ref_table". This identifier is free to choose and shouldn't be interpreted as a name of a table. In order to resolve the correct table name, which is stated in the configuration, the page id of the reference record is now used. This allows the TypolinkSoftReferenceParser to read the according page TSconfig and to set the correct table name. Resolves: #95380 Releases: master, 10.4 Change-Id: I28817a7267a107df27828d99f7e0cf2eeaaf2de1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72202 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Henrik Ziegenhain <henrik@ziegenhain.me> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Henrik Ziegenhain <henrik@ziegenhain.me> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 15 Nov, 2021 4 commits
-
-
The ConditionMatcher tries to resolve the current page id from global variables. One of this possibilities uses the cmdMap that is sent to the DataHandler. This patch ensures that the correct target uid is used to resolve the page id. Resolves: #95967 Releases: master, 10.4 Change-Id: I0fb7968c3118f2ab78c1cbb1dda3643e9f2f450e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72119 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Benjamin Franzke authored
empty() returns true if a record contains 0 as value. Therefore isset() needs to be used instead. The corresponding fix that was introduced with #91145 to workaround this flaw is removed again. Change-Id: I7286cf2337e3d7c942844881f95041bc54f8e811 Resolves: #95972 Related: #91145 Releases: master, 10.4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72117 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
-
This patch applies the current recommendations for BASH scripts see https://github.com/koalaman/shellcheck#readme. Resolves: #95964 Releases: master, 10.4 Change-Id: I21ba18cb151acc0ff8f33a2135ef289669d15bab Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72179 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Christian Kuhn authored
Brings a series of core v11 relevant PHP 8.1 E_ALL preparations and a couple of minor details. composer req --dev typo3/testing-framework:^6.13.0 mikey179/vfsstream:^1.6.10 composer req --dev typo3/testing-framework:^6.13.0 mikey179/vfsstream:^1.6.10 -d typo3/sysext/core/ --no-update Change-Id: I140866e8fb7014efbc33b7c1f25b2f840bd19ce2 Resolves: #95979 Releases: master, 10.4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72177 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 11 Nov, 2021 3 commits
-
-
Currently, the value of `USdateFormat` is disregarded because the corresponding property, `FormEngineValidation.USmode`, is set to zero regardless in `FormEngineValidation.initialize()`. This change will ensure that `USmode` will remain 1 without conflicting with core functionality that relies on `USmode` being set *before* `initialize()` is called. Resolves: #86679 Releases: master, 10.4 Related-to: #91105 Change-Id: I5584ca7fe92742e28147f9883fedf53e0556f1b1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72116 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Benni Mack authored
This reverts commit 7bfe6f76 as this has some side-effects with absolute paths. Reverts: #95379 Resolves: #95959 Releases: master, 10.4 Change-Id: I0065bb2db480f29fea12890cdfb3d34b57c94eef Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72115 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Native time fields (dbtype) in the record list are now displayed independent from the server timezone. Resolves: #92962 Releases: master, 10.4 Change-Id: Ie9075378e67d0c302b126db78751992789fae29c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72113 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 10 Nov, 2021 6 commits
-
-
Redirects to target with LinkHandler uri 't3://' need a bootstrapped 'TypoScriptFrontendController' and parsed and executed TypoScript, which is done later in the middleware stack for normal requests. Thus RedirectService bootstraps 'TypoScriptFrontedController' to generate uri for LinkHandler uri. At this point global '$GLOBAL['TYPO3_REQUEST']' has not been in set, and the fallback to create it from GLOBALS would not have correct site and siteLanguage attributes set, which would fail to evaluate TypoScript conditions correctly like 'fallbackLanguageIds' array check for siteLanguage attribute, as null is returned instead of an array. For v11 this was already fixed through moving to passing the PSR-7 request and initalizing TSFE with passed request in #92666 and the coresponding patch. This patch sets a '$GLOBAL['TYPO3_REQUEST'] to the current '$request' to avoid 'InvalidTypoScriptConditionException' if page is in FE debug context (ex. DebugPreset). If no redirect is found to be handled, that temporarly global request object is removed, to handle it through the normal middleware stack. Resolves: #95882 Related: #92666 Releases: 10.4 Change-Id: I6d7bff643fa2440e3986e4362c1882d53db1bb67 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72074 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Sybille Peters <sypets@gmx.de> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Text cropping on texts with way more than 1000 characters triggers regular expression compilation errors. The sweet spot was determined to a value of max 962 characters, thus leading to internal 'preg_match' error state and throwing 'Compilation failed: regular expression is too large' warning. The patch crops text in multiple chunks and reassembles the chunks until crop position was reached to avoid this internal error exceeding the max regular expression pattern length. Further tests are added to cover this scenario. Resolves: #77642 Releases: master, 10.4 Change-Id: I15b778370df0d0a3d3087a0b199c3e16f7a46add Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72149 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Using references instead of absolute URLs has the following advantages: - If a target section is moved, the URL in a :ref: linking to it is updated automatically - It is possible to maintain the links to the other docs repository in a central place (Settings.cfg). This way, it is possible to link to the same version of a manual in a lower branch (e.g. 10.4) by changing the link in one place The above results in a better user experience (stay in information for same version when linking across docs repos) and less broken links (in the future). Resolves: #95948 Releases: master, 10.4 Change-Id: I84d801a75424bd94b4fa15aecb17a6085af07c36 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72148 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
FlexForm Section can be added before content element is saved. This is done by ensuring that processedTca have a value for list_type. Earlier the pi_flexform was ignored as the default values on create before save was empty. Resolves: #81684 Releases: master, 10.4 Change-Id: I62e03cbbd93e8785f58c24dad1e573e8b5e0202b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72147 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
The method signature of Query::locicalOr() is very misleading because it only states there is one method argument $constraint1. Actually, the method does accept any number of arguments, evaluated via func_get_args(). It also accepts any number of arguments if $constraint1 is an array of constraints. This leads to multiple issues when working with phpstan and also when simply using an IDE which does not understand the internal magic. The goal is to state, that logicalOr() needs at least two constraints but also accepts any number of further constraints. Since that requires a breaking change, the method signature can only be fixed partly for now. $constraint1 remains as is, a 2nd argument $constraint2 is introduced, null by default to make it optional and a variadic argument ...$furtherConstraints is also introduced. This approach keeps the bc promise but also lays the foundation for further changes in the next version. Releases: master, 10.4 Resolves: #95938 Change-Id: I2a605cb4f42ec5324d973b63cf838278287de516 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72144 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- Remove information about bug which no longer exists - Link to redirects documentation - Remove example for redirect module because such a redirect may not be the best example to handle with EXT:redirects because permanent redirects with regex might be better maintained in webserver configuration, examples are best kept in redirects documentation and example for this specific redirect and the regex for it can be easily found elsewhere. Resolves: #95944 Releases: master, 10.4 Change-Id: Ia8f01f37228efc88c2675e342a96738b5e20ae6c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72146 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 09 Nov, 2021 6 commits
-
-
The first array entry for "$data" is the replacement for "%s" in vsprintf. The order has been swapped, so the wrong e-mail is the replacement instead of the localized error message. This has been recently fixed in master with #95459. Releases: 10.4 Resolves: #95444 Related: #95459 Change-Id: I046f604460bbe95788b076ff87cfc9319f7b0ab6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72105 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Nikita Hovratov <nikita.h@live.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
The method signature of Query::locicalAnd() is very misleading because it only states there is one method argument $constraint1. Actually, the method does accept any number of arguments, evaluated via func_get_args(). It also accepts any number of arguments if $constraint1 is an array of constraints. This leads to multiple issues when working with phpstan and also when simply using an IDE which does not understand the internal magic. The goal is to state, that logicalAnd() needs at least two constraints but also accepts any number of further constraints. Since that requires a breaking change, the method signature can only be fixed partly for now. $constraint1 remains as is, a 2nd argument $constraint2 is introduced, null by default to make it optional and a variadic argument ...$furtherConstraints is also introduced. This approach keeps the bc promise but also lays the foundation for further changes in the next version. Releases: master, 10.4 Resolves: #95889 Change-Id: Ife1be32d99371b82a84b6f6d800a58d242c8ff0d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72099 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
To ease the work with phpstan and IDE's, some types in persistence related classes of extbase are now either fixed or more specified. Releases: master, 10.4 Resolves: #95885 Change-Id: I2a784bd3ffaae651dd67dd939ef13e5efcb2ead6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72112 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Oliver Bartsch authored
It's possible to query for deleted records in DB Check "Full search". Such records can then be restored only or additionally restored and directly edited. The icon for the latter action was broken, since a non existing icon identifier was used. This is now fixed, using the correct icon identifier. Resolves: #95923 Releases: master, 10.4 Change-Id: I7da25198efe731a9ccba9e673c8c55e42760b233 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72100 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
Oliver Bartsch authored
In prior versions, creating a new page via the context menu inserted the new page "inside". This however changed to "after" in v8, leading to misbehavior, especially for non-admins, as they are usually not allowed to create pages on pid=0. This is now fixed by restoring the previous behavior of inserting pages "inside" instead of "after". Resolves: #81405 Releases: master, 10.4 Change-Id: I6a941c3e015189a471d0c136c81f1e5698426dbb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72097 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
The pagination feature in DB Check "Full search" did not work, since the defined offset was not added to the query. This is now fixed by checking for a comma separated string, which would therefore contain both an offset and the limit. In case both values are given, they are now properly added to the query. Resolves: #95922 Releases: master, 10.4 Change-Id: Id461b98a9818c3b55b34f93041a9c0950e68f634 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72096 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 08 Nov, 2021 5 commits
-
-
The TCA types "group" and "select" are both using the relation handler to resolve items from foreign tables. Previously, delete placeholders were still fetched in a workspace. This is now fixed by properly handling the delete placeholders before fetching the items. Resolves: #88144 Releases: master, 10.4 Change-Id: Ieca2acb16af10982d16af981d0e302b2ea29ae1d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71929 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
PHPDoc block for method PageSlugCandidateProvider::getCandidatesForPath() had incorrect return type of string[]. This is changed to array<int,array<string,mixed>>. Resolves: #95901 Releases: master, 10.4 Change-Id: I9a7cd326acf3dd88bfb2833b50b135a9d84164eb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71928 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
The forced scheme needs to be checked if not empty and not only if existing. The regression has been introduced with #90228. Related: #90228 Resolves: #95796 Releases: master, 10.4 Change-Id: Ia941142aacc688ddd02d3f7f45d3ce493821ce68 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71927 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Add the missing samesite cookie option after the logout from the install tool which leads to an error in the browser console. Resolves: #95270 Releases: master, 10.4 Change-Id: I399e3db96bbaaeef7a79caa43ac221a3d5c30f0a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72060 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Change requirement from cogpowered/finediff to lolli42/finediff. This was already done for v11 - due to problems with PHP 8 in the lib cogpowerd/finediff. Additionally, due to strict type checking, a cast to string must be perfomed in DiffUtility::makeDiffDisplay(). The new library also comes with better support for multibyte strings and still supports PHP 7.2 so it can be used in v10 as well. Finediff provides an extendable diff functionality which can be used by extensions as well and is used in the core in the DiffUtility class. Since the change for v11 was a bugfix, but for v10 it is not, change is declared as TASK and a new patch is created. Resolves: #95900 Related: #95742 Releases: 10.4 Change-Id: I67f1c22d0c59386071459c2670a3069d563eb0bb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72075 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
- 05 Nov, 2021 5 commits
-
-
This commit improves the overall readability of the ext:redirects documentation. Releases: master, 10.4 Resolves: #95884 Change-Id: Ia15d2f909dcdbb301152142c8fd32989a12687fb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72067 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
Width and height of an image is stored in translatable metadata records. These properties are extracted by FAL API when a new image is uploaded. The TYPO3\CMS\Core\Resource\Index\Indexer::updateIndexEntry method uses the MetaDataAspect to save the new file dimensions. As the MetaDataAspect has no support for multi-language, it only updates the default language. A new PSR-14 event listener is added on AfterFileMetaDataUpdatedEvent to overcome the lack of translation support. It updates the width and height of all corresponding sys_file_metadata translations. Wrong dimensions leads to rendering issues in the frontend when the image is cropped as the crop area can't be calculated properly. Resolves: #87162 Releases: master, 10.4 Change-Id: Ic1d66a24f23f4312325b3f74e5959b2d2b3c1cf6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71925 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
ScriptViewHelper and AssetViewHelper do not directly output any tag, but only pass the arguments to AssetCollector. Therefore the tag attribute values must not be HTML encoded. To achieve that, we use a subclass of TagBuilder before the tag is initialised, which does never encode attribute values. The tag view helper inheritance is kept because the tag builder nicely abstracts attribute handling, which otherwise would have to be duplicated. Also ensure that rendered children will not be encoded as this string is used as CSS or JavaScript, where HTML encoding won't help or rather break the code. Resolves: #92706 Related: #92284 Releases: master, 10.4 Change-Id: I823ad167ccbd52e9e0f3ad9bb3d54f554a985fef Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71926 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
EditableRestriction in linkvalidator checks which fields are editable Doing so, it also considers the allow / deny types (explicit_allowdeny in be_groups). However, there were previously 2 problems which resulted in broken links not displayed for some tables (e.g. in tx_news_domain_model_news): 1. If the type was '0', no value was written to tx_linkvalidator_link. element_type. 2. If ctrl => type was set in TCA, but authMode is not or authMode_enforce == 'strict', the check should not be performed. Both problems are now fixed. The fix for problem 1 requires a rechecking of links so that the element_type field will be filled. Resolves: #94381 Releases: master, 10.4 Change-Id: Id8c6db57baab7e000130198e508b7c437d87faac Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71924 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
Resolves: #95865 Related: #95816 Releases: master, 10.4 Change-Id: Ic9fecfbe07abf98af8d9b8f73d54f3482643c372 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71923 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 04 Nov, 2021 4 commits
-
-
Resolves: #95868 Releases: master, 10.4 Change-Id: Iffc8ed042f4990b132c28a0ff7b4d80ffca530ac Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71922 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Anja Leichsenring authored
FluidEmail view object is null after deserialisation causing an error when flushing the file spool queue. Ensure the view is initialised when generateTemplatedBody() is run. Resolves: #92394 Related: #91763 Releases: master, 10.4 Change-Id: I5c8025a9526af00aa520213a9c5c105d8d7d3ccf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65844 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Simon Gilli <typo3@gilbertsoft.org> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Simon Gilli <typo3@gilbertsoft.org> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72053
-
Resolves: #95868 Releases: master, 10.4 Change-Id: I443ba87dd97e1efacbaf441a1263dd47ec1e1aa2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71921 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
search_field value from session is never used again anymore, fixed that regression Resolves: #94898 Releases: 10.4 Change-Id: I283a2c29cdfa0f8f861712d4c16df04cbf880e6b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72051 Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-