- Oct 12, 2021
-
-
Susanne Moog authored
Releases: master Resolves: #95574 Change-Id: I2587d67c09b317a6a14681fdf2c77a702d0be734 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71552 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
-
Oliver Bartsch authored
The WorkspaceMenu JavaScript module is used to update the topbar elements, related to workspaces. The required state handling is now simplified and does no longer rely or manipulate "global" configuration (top.TYPO3.configuration or top.TYPO3.Backend). This therefore also allows to remove the "inWorkspace" value, set in the BackendController. Additionally, the "check icon", in front of the current selected workspace menu item, is now properly updated again. Resolves: #95503 Releases: master Change-Id: Ic2bce429c07e62b86d71f32f143280fb20a73cc2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71478 Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
-
Oliver Hader authored
Allow a list of HTML tags in the help content just as for the configuration details. Resolves: #95152 Releases: master Change-Id: Icc2e0b60a1ed86f67604e276322ec24162234a95 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70980 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
-
Wouter Wolters authored
composer req --dev composer/package-versions-deprecated:^1.11.99.4 composer req --dev friendsofphp/php-cs-fixer:^3.2 composer u mikey179/vfsstream Resolves: #95570 Releases: master Change-Id: Ic2321dde785113e16d200b649cd7da9a91de9d71 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71537 Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
-
- Oct 11, 2021
-
-
Oliver Hader authored
Resolves: #95573 Releases: master, 10.4 Change-Id: I13742f80588d8d1d566d08e7b51c165a5139fe50 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71538 Reviewed-by:
-
Christian Kuhn authored
The install tool has a special standing due to the FailSafeContainer. The default functional test set up however creates a 'full' container. This triggers a slightly different code path in ViewHelperResolver, which we need to work around a bit. Resolves: #95568 Releases: master Change-Id: I0eb8ad905baedf50d7cee74b30625573d1b854ae Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71535 Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Reviewed-by:
-
Francois Suter authored
Fixes some undefined array key errors which happen in some specific scenarios related to workspaces usage. Resolves: #95564 Releases: master Change-Id: I22fde56a506ae327ed0121bc68882996da7728df Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71532 Tested-by:
-
Christian Kuhn authored
enableRuntimeCache() has been deprecated with #93038, with all calls being removed. #94772 re-introduced one case, probably during rebasing. Resolves: #95569 Related: #93038 Related: #94772 Releases: master Change-Id: I5f072f85d5714496870a5fdbb4694fd3426a56a5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71536 Tested-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
-
Nikita Hovratov authored
This resolves a todo in Tooltip.ts, where we've waited for an updated types definition for bootstrap. Now some new methods, like Tooltip.getOrCreateInstance, are known to TypeScript and can be used, without setting an ignore comment. Command used: > yarn upgrade @types/bootstrap --latest Resolves: #95553 Releases: master Change-Id: I4f9c33c735580ebb02d29b3910403f03c01a5913 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71522 Tested-by:
-
Christian Kuhn authored
Yet another series of PHP 8 stabilizations for ext:lowlevel QueryGenerator. This time found by functional tests when error handling in functionals is turned off. * Various null coalescence within class itself * A test setup change which string_replace()'ed within a serialized string, which invalidates length specifications. Fixed by serializing after replace operations, instead of before. Resolves: #95562 Releases: master Change-Id: Id0b06f1059bfb39296ccdb9cc37ff610652ba3f5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71531 Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
-
Francois Suter authored
When accessing the Workspaces module in the LIVE workspaces, the underlying code tries to access the list of stages although the LIVE has none. To avoid downstream undefined key errors, return empty list up front. Resolves: #95566 Releases: master Change-Id: If8178e7968d7a6b094c66f1b54a6f47b0a5762a7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71533 Tested-by:
Xavier Perseguers <xavier@typo3.org> Tested-by:
-
Sybille Peters authored
If no allowed languages are defined for a BE user / group ([allowed_languages] is not set), only broken links in records of the default language were shown for editors. This was incorrect and this patch fixes the problem. Broken links in translated records will now always be shown for editors (if they have write access to the records). Background information: Linkvalidator checks if the current editor has write access to the elements / fields in which the broken links are contained. This ensures that only broken links will be displayed, if the editor can fix them. Resolves: #95467 Releases: master, 10.4 Change-Id: I53f507889a9a275e7aa42994549976a9d38489b7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71430 Tested-by:
-
Helmut Hummel authored
There are few cases where the resulting path from FilePathSanitizer is needed and used as absolute path to a private file. For these usages the file now is returned early. Additionally the logic to make a relative path out of an absolute path is now relaxed a bit, so that legacy usages of this API won't fail any more. An exception is still thrown, when a path from Composer package is requested, that can not be resolved to a public path. Resolves: #95481 Resolves: #95495 Releases: master Change-Id: I8df7d74e6e71154be0508a96cdc19821beeb5ecb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71457 Tested-by:
-
Christian Kuhn authored
One of the functional test related extensions still sets 'exclude' TCA property for a transOrigPointerField, which is deprecated and migrated away since fixing #89550. Resolves: #95561 Related: #89550 Releases: master Change-Id: I1f5bce2ef3ef6daee0ce57fb0e34bb4a48022fdb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71530 Tested-by:
-
Oliver Bartsch authored
This fixes a couple of undefined array key accesses in BackendUserAuthentication->modAccess(). Besides, the code is a bit simplified and some comments are added / fixed. Resolves: #95560 Releases: master Change-Id: I0fb20e1b9783fb770ff344bc0b4dc339f4a2ad50 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71529 Tested-by:
-
Stephan Sellner authored
Releases: master Resolves: #95490 Change-Id: I8c7f055182e9a4da8ea5a7a4bd946cc69ce26e0f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71455 Tested-by:
-
Stefan Bürk authored
In PageSlugCandidateProvider the pageCandidate MPVar has been build conditional based on of original MPVar was set. The check did not checked for not existing index which throws an 'undefined index'. This patch uses the correct check to prevent that warning. Resolves: #95546 Releases: master Change-Id: Ib2478b45b769a50ab14eddd220ebbf02a19d3adb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71516 Reviewed-by:
-
Stefan Bürk authored
RedirectsServiceTests simulate frontend requests without executing them really, which prevents from running through the FE Bootstrap stack, thus not all needed stuff are setup correctly, thus throwing a warning that $GLOBALS['BE_USER'] is not defined. This patch initialize a backenduser for the RedirectServiceTest to setup a correct BackendUser object, thus mitigating this warning. Resolves: #95548 Releases: master Change-Id: I8318738e22761f172383db3b981779e331043f3f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71518 Reviewed-by:
Guido Schmechel <guido.schmechel@brandung.de> Reviewed-by:
-
Stefan Bürk authored
Tests in SlugServiceTest from ext:redirects depend on an initialized LanguageService, which has not been done as there are no real frontend request executed, thus the normal FE Bootstrap was not run. This leads to undefined index errors because $GLOBALS['LANG'] is not initalized. The patch initalizes the LanguageService using the Bootstrap::initalizeLanguageObject() in the setup(). Resolves: #95547 Releases: master Change-Id: I53fb8877dd2692968c342e8df266f6268384ed1f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71517 Reviewed-by:
-
Stefan Bürk authored
Initializing LanguageService in $GLOBALS['LANG'] with Bootstrap::initalizeLanguageObject() needs a proper setup $GLOBALS['BE_USER']. The patch moves Bootstrap::initialzeLanguageObject() from abstract testcase to the corresponding setUp() methods user and admin recycler tests after the corresponding backend user is set up. Furthermore some assertions are fine tuned to prevent array access warnings in tests. Resolves: #95549 Releases: master Change-Id: I3a9fed0a6f83e9481b169fb4a476ba2e2235e483 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71519 Tested-by:
-
Stefan Bürk authored
BrokenLinkRepositoryTest of ext:linkvalidator initalizes beuser dynamicly for tests and testdatasets. LanguageService has been initializied once as setup, before a valid beuser was initialized. Thus undefined index BE_USER warnings has been created. This patch (re)initializes the LanguageService using the corresponsign Bootstrap::initializeLanguageObject() method after each backend user initializing, and remove the single to early call from setUp(). Resolves: #95552 Releases: master Change-Id: I89f8e0e6092c1578ef57c20e52b950b9a73996a3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71523 Tested-by:
-
Stefan Bürk authored
Install tool has been trying to connect to the database before checking if a bare minimum of configuration is given to. This has been done to decide if the database connect step needs to be shown. Starting with php8.1 this fails hard and the step is not shown, thus an installation cannot be finished. This patch change the checking order and checks for the bare minimum of configuration first, before try to connect to the database. Build/Scripts/runTests.sh -s acceptanceInstall -p 8.1 -d sqlite Build/Scripts/runTests.sh -s acceptanceInstall -p 8.1 -d mariadb Build/Scripts/runTests.sh -s acceptanceInstall -p 8.1 -d mysql Resolves: #95545 Releases: master, 10.4 Change-Id: I9923198b26f86e44fd6c1f6655195faa0c79895e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71514 Tested-by:
-
Helmut Hummel authored
It was a conceptual mistake to move storage 0 base path outside the document root (public path), because this complete compatibility layer relies on the fact that this storage is public. Moving it outside the public path, implicitly made this storage private, with all logical consequences like eID public URLs. This of course isn't desired and a breaking change of behaviour. With moving the base path back it means, that trying to access this BC layer with paths that are not within the public path, will not work any more. This is fine though, because this never worked before TYPO3 11.5 anyway. The reason why this was made working was EXT:form, which used the storage 0 compat layer for resolving form definitions from extensions, which did not work, when installing extensions into vendor folder (instead of the still current default, where extensions are installed in public folder). Accessing public resources from vendor installed extensions will still work with this change, because the public asset URL will automatically be calculated, but accessing private resources will thrown an exception to clarify that the storage 0 compat layer is not made to make this possible. Also fix form framework to not rely on FAL compatibility layer during form loading. Resolves: #95543 Relates: #95437 Releases: master Change-Id: Ie218dbb8ace9999f2bead77b671ae87f6ad46170 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71512 Tested-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
-
Stefan Bürk authored
Public property $cObj for plugins has been deprecated in v11 with #94956 and setContentObjectRenderer() method has been introduced as replacement. If this method is missing, a deprecation message is triggered. This patch inserts the class name of the plugin into the message, to make it easier to determine where the new method is missing. Resolves: #95554 Releases: master Change-Id: Iffae1fcbd2f59bd4fe353e585dd5f41914bcc760 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71524 Reviewed-by:
Stephan Großberndt <stephan.grossberndt@typo3.org> Reviewed-by:
-
Nikita Hovratov authored
This resolves a todo, where a test was blocking a method of Clipboard to be protected. The test is now adjusted as such that it now calls a real public method and extracts the needed information from it. Resolves: #95556 Releases: master Change-Id: I62dd988481ce807cb3716810fc7a6dd2bf4e8842 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71526 Tested-by:
-
Helmut Hummel authored
* Use config API instead of env vars when building package artifact * Don't try to scan for extensions in Composer mode * Don't create extension directory in Composer mode, as the composer installer takes care of creating it if needed * Don't try to scan extension directory if it does not exist * Use package type instead of install path to distinguish core extensions Releases: master Resolves: #95483 Change-Id: I63ff42c301eba66e85471702fb03739374f7821c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71453 Tested-by:
Simon Gilli <typo3@gilbertsoft.org> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
-
- Oct 10, 2021
-
-
Benni Mack authored
This change addresses a regression of https://review.typo3.org/c/Packages/TYPO3.CMS/+/58829 where access-restricted pages (e.g. fe_groups restriction) under a sys-folder (e.g. 2021 for subpages categorized by the sys-folder 2020) to again return a 403 error to be properly handled by a proper error handler. This change adds tests to ensure this functionality is always working. Resolves: #92762 Related: #92225 Related: #84098 Related: #86346 Releases: master, 10.4 Change-Id: I7e9a96fddd24abc83f55c85148965b654a0fede7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69306 Tested-by:
-
Stefan Bürk authored
CleanerTasks build a query checking if tstamp tca config is checked. Using null coalescing operator to sanatize access in the condition. Resolves: #95550 Releases: master Change-Id: Ib4a34def6727d3a7f39f7a734a9a84bbb4697e3b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71520 Reviewed-by:
-
Stefan Bürk authored
This patch fixes undefined index/offset warnings in ext:lowlevel QueryGenerator using null coalescing operator. Resolves: #95551 Releases: master Change-Id: I26fd0bd77bdc086916a57460680b06de689134db Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71521 Tested-by:
-
- Oct 09, 2021
-
-
Oliver Bartsch authored
This correctly sets "subst" as a value of the softRefParams array. Previously "subst" was set as key, which only worked because of a non strict "in_array" check, which also returned TRUE for this case, but then broke with the refactoring in #94687. Additionally the regular expression of the UrlSoftReferenceParser, used to find urls in content, also got extended in #94687. This is now partially reset to not longer match links in tag attributes. This otherwise would lead to duplicate entries, since those urls are already matched by the TypolinkTagSoftReferenceParser. The impact of the changed regular expression was overlooked beforehand, due to the bug in LinkAnalyzer. Resolves: #95449 Related: #94687 Releases: master Change-Id: I3ca134cd1eed95b8563335708e393f5b5fa79420 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71511 Tested-by:
-
Jochen Roth authored
Adding a file collection to the file links content element leads to undefined array key warning. This is fixed by setting the itemsCriteriaField name to "files". Resolves: #95514 Releases: master Change-Id: I3afb5c57e2be0a7ac776f5dbd75705aa9120dbc5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71507 Tested-by:
-
Oliver Bartsch authored
The "displayThumbs" module setting is fetched two times in the FileBrowser. One time to determine whether thumbnails should be displayed and a second time to set the current value of the display thumbnails "toggle". However, the default values of those two cases differed, which then led to a default state where the "toggle" was active, while no thumbnails were displayed. This is now fixed by using the same default for both cases. Resolves: #95425 Releases: master Change-Id: I9cdf81a28aceb91d5f419332d24337b22de2a575 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71515 Tested-by:
-
Nikita Hovratov authored
The coalesce operator has a relatively low precedence over other operators. If used as part of other expressions, it is almost always necessary to wrap it in parenthesis. Otherwise unexpected behaviour or undefined array key errors (in PHP 8.0) may occur. Resolves: #95482 Releases: master, 10.4 Change-Id: I4ddecdbeab03c215477f77742674ded01bc29257 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71449 Tested-by:
-
- Oct 08, 2021
-
-
Benni Mack authored
When showing required dependencies (= extensions) in Extension Manager, e.g. for distributions - downloading the Introduction Package, the remote (e.g. "ter") needs to be set for displaying purposes. Resolves: #95544 Releases: master Change-Id: I4cc2ca1af7d8acaaac3dfb4d8fe7ca3461749610 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71510 Tested-by:
Benjamin Kott <benjamin.kott@outlook.com> Tested-by:
-
Robert Kärner authored
Access to $GLOBALS['BE_USER'] must be protected by the neccessary fallbacks, as no backend user might be logged in when an exception is thrown in the frontend. Resolves: #95538 Releases: master Change-Id: I03e21c9ef8f1770ed3d2fa72bd6cd99d7e6fc3cd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71505 Tested-by:
physikbuddha <r.kaerner@oranto.de> Reviewed-by:
-
Oliver Bartsch authored
The confirmation password, required for accessing the install tool through the backend, now uses the autocomplete attribute to prevent password managers from initiating a "change password" workflow. Resolves: #92969 Releases: master, 10.4 Change-Id: I27bc81e7ebaa9684b4e15c7208841ca5e3a4338d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71501 Tested-by:
-
Marcel Schüßler authored
When using the "saveAndClose" option for a newContentElementWizard item, the target link forwards directly to the record_commit route instead of FormEngine. Previously the parameters for this link were added to an array, which was then never reset after used for the link creation. This therefore resulted in multiple elements were created as soon as the "saveAndClose" option was set multiple times. This is now fixed by not using a single use variable anymore, but directly building the data array in the link, like it's already done for the FormEngine links. Releases: master Resolves: #95526 Related: #95277 Change-Id: I897acd376ce44c6f26c27dc7ddd927302e5be8bb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71488 Tested-by:
-
Jochen Roth authored
The paths for source set images is currently prefixed with a slash which causes duplicated slashes at the beginng of the path so images are not displayed anymore. This has been fixed by removing the url prefix for source sets. Resolves: #95493 Releases: master Change-Id: Ieba7c4b380a9c8c14d73b83909b891dd634a041d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71508 Tested-by:
-
Alexander Schnitzler authored
Releases: master Resolves: #95258 Change-Id: Idddbd4c449e2dc891c91f466614f04a8770d5815 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64429 Tested-by:
-
Oliver Bartsch authored
This fixes some undefined array key warnings, that appear on frontend requests. Resolves: #95542 Releases: master Change-Id: I40e6fb10b618f0487ecd763afea2b67ee2eabb7e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/71509 Tested-by:
-
