- Jun 06, 2024
-
-
Garvin Hicking authored
The use of the backtick operator inside the help output leads to an error message: Build/Scripts/runTests.sh: line 175: --: command not found on macOS (probably others, too). This patch replaces the backticks with normal quotes. Resolves: #103988 Releases: main, 12.4, 11.5 Change-Id: Ib6809dc6943a98e4d45d04f4ec02601e830518cd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84463 Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
core-ci <typo3@b13.com> Reviewed-by:
-
Andreas Kienast authored
With Chrome 125, changes in the drag&drop handling were introduced [1] that trigger a text selection when dragging nodes from the page tree toolbar. In the `dragstart` handler, the default action is now prevented. [1] https://developer.chrome.com/release-notes/125#interoperable_mousemove_default_action Resolves: #103877 Releases: 12.4, 11.5 Change-Id: Iad75db78bba3e7b5ad01a568dcab2eb770f1c4a2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84509 Tested-by:
Benjamin Franzke <ben@bnf.dev> Reviewed-by:
-
- Jun 05, 2024
-
-
Benjamin Franzke authored
Workaround a PHP issue which will produce an open_basedir restriction warning if `is_dir()` is used on a regular file when the trailing slash is provided. Resolves: #103943 Releases: main, 12.4, 11.5 Change-Id: Iaa83658113ff8abb0ab8051b519f76135effd627 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84437 Tested-by:
-
Christian Kuhn authored
Sometimes - for unknown reasons - a session gets lost in acceptance tests. Tests then hang in BE login waiting for BE load and fail with a timeout. We now catch this timeout and relogin, and also enable cookie debug output to increase chances to fix the real issue. Resolves: #103981 Related: #103086 Releases: main, 12.4, 11.5 Change-Id: I0b10118968933b52523bbee8f8f608db60ad884e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84502 Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
-
- Jun 03, 2024
-
-
Stefan Bürk authored
The `symfony/yaml` package provides the `yaml-lint` commandline tool to lint yaml files. This change introduces yaml file linting checks using the symfony tool, differencing `Services.yaml` from other yaml files. Resolves: #103931 Releases: main, 12.4, 11.5 Change-Id: I9442b38c439fb5f2d5507ca0ab70235b2dfd194a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84482 Tested-by:
-
- May 27, 2024
-
-
Stefan Bürk authored
With PHP 8.4 marking method parameter implicitly nullable is depreacted and will emit a `E_DEPRECATED` warning. One recommended way to resolve this, is making it explicitly nullable using the `?` nullable operator. [1] In cases, where are implicitly nullable parameter exists before not-nullable parameters in a method or constructor, making it explicitly nullable will emit a Optional parameter <paramname> declared before required parameter <paramname> is implicitly treated as a required parameter since PHP 8.0 [2]. This change adds the `?` nullable operator and removes the null default value for the first parameter, which mitigates both issues. This prepares the way towards PHP 8.4 compatibility. [1] https://php.watch/versions/8.4/implicitly-marking-parameter-type-nullable-deprecated [2] https://php.watch/versions/8.0/deprecate-required-param-after-optional Resolves: #103927 Releases: main, 12.4, 11.5 Change-Id: I0ba574769e5b95852379aa30f...
-
Stefan Bürk authored
With PHP 8.4 marking method parameter implicitly nullable is depreacted and will emit a `E_DEPRECATED` warning. One recommended way to resolve this, is making it explicitly nullable using the `?` nullable operator. [1] In cases, where are implicitly nullable parameter exists before not-nullable parameters in a method or constructor, making it explicitly nullable will emit a Optional parameter <paramname> declared before required parameter <paramname> is implicitly treated as a required parameter since PHP 8.0 [2]. This change removes the `null` default value and adds the `?` nullable operator to the previousException parameter for the `\TYPO3\CMS\Backend\Form\Exception\DatabaseRecordException` constructor. This prepares the way towards PHP 8.4 compatibility. [1] https://php.watch/versions/8.4/implicitly-marking-parameter-type-nullable-deprecated [2] https://php.watch/versions/8.0/deprecate-required-param-after-optional Re...
-
Stefan Bürk authored
`\TYPO3\CMS\Core\Tests\Unit\Database\ConnectionTest` containes code to mock Connection methods conditionally, based on their existance surrounded by a `@todo` comment to remove this, when `doctrine/dbal` has been required with 2.11.0 as minimal version. The version raise has been done already a long time ago, however the removal of this conditional test mock has been missed. This change removes the conditional mocking now. Resolves: #103929 Releases: main, 12.4, 11.5 Change-Id: I4cc2d5942149f69e044c25379c82388f1c4b9f45 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84423 Tested-by:
-
- May 25, 2024
-
-
Georg Ringer authored
The configuration `foreign_table` of the type `select` is optional. Add a check to avoid PHP warnings. Resolves: #103825 Releases: main, 12.4, 11.5 Change-Id: I65925bae287a0ed340c67923ac4e4a2c72ce9d28 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84394 Tested-by:
-
Anja Leichsenring authored
The test setup used a dataProvider and in order to get it's own setup right, it reverses and resets leftover instances from the previous run. It is way easier to split the test setup according the admin flag, that decides about the resets, and run on a clear dedicated environment. Additionally, the system under test is in itself a mocked instance, which is neither necessary in this case, nor generally recommended. The mock has been resolved. Resolves: #103901 Releases: main, 12.4, 11.5 Change-Id: If40ef38a0e0fc2e73dd5f0bc8caff923cc48d661 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84393 Tested-by:
-
- May 22, 2024
-
-
Christian Kuhn authored
Less jobs while keeping general pipeline times low. * Simplify runner cache configuration * sqlite pre-merge 3 instead of 5 jobs * sqlite nightly 4 instead of 6 jobs * merge checkIntegrityPhp to general integrity job * merge checkGruntClean to general js job * merge php lint jobs into one * avoid composerInstall for unitJavascript * merge acceptance install jobs into less jobs * update acceptance test matrix to run less jobs in nightly while still catching many configuration permutations in addition to pre-merge Note backports are similar but deviate in details. Change-Id: I832543e002824977a98d3ffb35c3d08355b1f5be Resolves: #103869 Releases: main, 12.4, 11.5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84347 Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>...>
-
- May 21, 2024
-
-
Ayke Halder authored
Use all available CPUs with `Build/Scripts/runTests.sh -s lintPhp`. Note podman CI is configured with a cpu-share to prevent starving other jobs when one is greedy, so this change is ok with CI, too. Resolves: #103864 Related: #103851 Related: #102385 Releases: main, 12.4, 11.5 Change-Id: I1cb7079f119677b36d6f4004398ae24bd8c5d284 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84319 Tested-by:
-
- May 17, 2024
-
-
Wouter Wolters authored
Use parallel runner to use more than 1 CPU. composer update \ composer/semver \ symfony/polyfill-mbstring \ symfony/polyfill-php80 \ symfony/polyfill-php81 composer require --dev friendsofphp/php-cs-fixer:^3.57.1 Resolves: #103851 Releases: main, 12.4, 11.5 Change-Id: I59b5e2566a385792cad1b6c11b9b84b63fd21b98 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84290 Tested-by:Andreas Kienast <a.fernandez@scripting-base.de> Tested-by:
-
- May 14, 2024
-
-
Andreas Kienast authored
The label for the delete action was encoded twice, leading to text issues in case special characters are involved. This commit makes use of `GeneralUtility::implodeAttributes()` to solve this issue properly. Resolves: #103827 Releases: main, 12.4, 11.5 Change-Id: Ia9f7ba5adf46b470a33b9065e49b8599a24fdfad Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84275 Tested-by:
-
Oliver Hader authored
Change-Id: I0ef0594cc0d3aefbacdc3e3bcbcaad685513b745 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84269 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
-
Oliver Hader authored
Change-Id: I5602a1ef868b9ebbdf0a8ffafae3650cfb845181 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84268 Reviewed-by:
-
Benni Mack authored
The "frame" parameter is no longer evaluated in the showpic eID as it allowed uncontrolled resource consumption. This parameter was actually never used by ContentObjectRenderer and existed since the initial commit and is therefore put behind a feature flag. Resolves: #103306 Releases: main, 13.1, 12.4, 11.5 Change-Id: I87019e58c078c8ccafc0b7ce42fe28b49dc068e4 Security-Bulletin: TYPO3-CORE-SA-2024-010 Security-References: CVE-2024-34358 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84256 Reviewed-by:
-
Oliver Hader authored
Resolves: #103303 Releases: main, 13.1, 12.4, 11.5 Change-Id: I2842cefd5dfc0aff920e61b5fd16f029db8ada4c Security-Bulletin: TYPO3-CORE-SA-2024-009 Security-References: CVE-2024-34357 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84255 Tested-by:
-
Benjamin Franzke authored
Encode non prepared output of BackendUtility::getRecordTitle. The string returned by getRecordTitle is only HTML encoded if the third parameter (`$prep`) is set to true, ensure that non-prepared usages are encoded on render. Resolves: #103782 Releases: main, 13.1, 12.4, 11.5 Change-Id: I96b9530d118a21163d6679ebf7120aa40c7ac7b6 Security-Bulletin: TYPO3-CORE-SA-2024-008 Security-References: CVE-2024-34356 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84254 Tested-by:
-
- May 11, 2024
-
-
Christian Fries authored
When addressing flexform fields in TSconfig, the dots of the field names have to be escaped with a backslash. Releases: main, 12.4, 11.5 Resolves: #103786 Change-Id: I6af70fcb80e9e155ba8259ec216c5199600c5a78 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84200 Reviewed-by:
-
- May 10, 2024
-
-
Christoph Lehmann authored
In advanced query the operator "is in list" makes value be an array. Then switch the field to a non-array field type, and you get the following TypeError: ``` htmlspecialchars(): Argument #1 ($string) must be of type string, array given. ``` This resets the array value to an empty string. Resolves: #103487 Releases: main, 12.4, 11.5 Change-Id: Ifc6ef7e90d49a05ecb4b6d4869eea13c151b1b2a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84188 Tested-by:
-
- May 06, 2024
-
-
Willi Wehmeier authored
The folder containing the charset conversion table files should have the unicode license.txt file. The license file is from https://unicode.org/license.txt Resolves: #103796 Releases: main, 12.4, 11.5 Change-Id: I2577fea6e1b5326cd45da622ec6fbbc563bc140a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84120 Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
-
- May 03, 2024
-
-
Oliver Hader authored
Commands: composer req 'enshrined/svg-sanitize:^0.18.0' composer req 'enshrined/svg-sanitize:^0.18.0' \ -d typo3/sysext/core --no-update Resolves: #103722 Releases: main, 12.4, 11.5 Change-Id: I9a20a46b27b3abbfd18f7ca6027e4def9ce5b59b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84138 Tested-by:
-
- May 02, 2024
-
-
Stephan Bauer authored
An error was previously shown and is now removed if no backend type is selected. Releases: main, 12.4, 11.5 Resolves: #103766 Change-Id: Ia83552de40abffb880244e8b0eb0f4c28f0e6637 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84113 Tested-by:
-
- Apr 23, 2024
-
-
Oliver Hader authored
Given a static route argument mapper is used - for instance one that allows values in the range of 1 to 100 - then generating an URL from a route with an out of scope `&value=5000` was still generating an URL. However, HTTP request to that URL would result in an 404 error. This change skips routes using out of scope values during the URL generation process to avoid pointing to invalid resources. Resolves: #103400 Releases: main, 12.4, 11.5 Change-Id: I11e12f29e294ec86bec948d3a922d4a56b231771 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84003 Tested-by:
-
- Apr 16, 2024
-
-
Georg Ringer authored
`DateTimeImmutable::setTimestamp()` requires the timestamp to be an integer. Resolves: #103588 Related: #99627 Related: #98045 Releases: main, 12.4, 11.5 Change-Id: I2dba1b3836063872fa04ea38d58b5bd499a8f7d1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83757 Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Tested-by:
Simon Schaufelberger <simonschaufi+typo3@gmail.com> Reviewed-by:
-
- Apr 15, 2024
-
-
Andreas Kienast authored
Resolves: #103615 Releases: main, 12.4, 11.5 Change-Id: I11f609625051f7dc6418596229bed49f282bc842 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83759 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
-
- Apr 10, 2024
-
-
Christian Weiske authored
`getEmptyObject()` does not call `getInstance()` which initializes the property, which is needed since PHP 8.0. TYPO3 v12 and later are unaffected, because the Container class has been removed there. Resolves: #102278 Releases: 11.5 Change-Id: I5f05b40990a2214cb86f2779b048149b2c931a2a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83707 Tested-by:
-
- Apr 08, 2024
-
-
Stefan Bürk authored
`Build/Scripts/runTests.sh` is the monorepo main dispatcher of script and tools to ensure same working state across developer host system and installation by using well defined containers. This mitigates issues with missing dependencies or wrong version of tools on develper machines. Until now local installation of `node` and `npm` in the matching version was mandatory to work with the node ecosystem like manage dependencies, executing node based tools or the build chain for CSS and TypeScript/JavaScript. This change adds now a `npm` dispatcher to `runTests.sh` similar to the `composer` command dispatcher introduced with #103045 to allow executing npm commands and defined scripts in `package.json` in a well-defined environment and removes the hard-requirement of installing it locally for new contributors. Added `runTests.sh` suite: * ./Build/Scripts/runTests.sh -s npm -- <npm-command-arguments> which allows now to using npm commands ...
-
Stefan Bürk authored
`\TYPO3\CMS\Backend\RecordList\DatabaseRecordList` provides the ability to modify the QueryBuilder used for the record list representation with $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS'][DatabaseRecordList::class]['modifyQuery'] after generic query information like default orderings and similar have been added. That is covered within the `getQueryBuilder()` method, which is used in other class methods, for example in `getTables()` where it is changed to a `COUNT()` query. MariaDB for example is picky about count queries using `order by`, `group by` or aggregation methods which are not reflected or added in the counter parts leading to a not so useful error like Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause or similar variants. This error message can be missleading for the case a order by has been used along with a COUNT() query. Hook consumer do not get the information if order-by can be added or should be left out, therefore maybe adding sorting conditions for a count query. This change now resets any order statements for the count-query like other places in the TYPO3 core. Resolves: #103427 Releases: main, 12.4, 11.5 Change-Id: Ie421993a1890dd6682d02f54203d538e6ae1b76c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83524 Tested-by:
Garvin Hicking <gh@faktor-e.de> Tested-by:
-
- Apr 07, 2024
-
-
Markus Klein authored
As documented by PHP, `\DateTime` or `\DateTimeImmutable` objects created with a timestamp only ('@12345678') as the first constructor argument will use UTC as TimeZone. Creating an object instance without any constructor arguments will use the `date_default_timezone_get()` timezone for the object - and setting the timestamp using `setTimestamp()` will not change the object's timezone. That means, that formatting the value will be done using the object Timezone and **NOT** the default PHP Timezone (`date_default_timezone_get()`). Consequently, this may lead to wrong interpretation of the displayed formatted value in the context of another timezone - if no timezone information (+0000/-0100) is included. This change streamlines this for a couple of places were it is expected to format date, datetime or time values for the current context timezone by ensuring objects get the current timezone set instead of `UTC`. Note: Changing the date default timezone on the fly after an object has been created will show a similar effect like using constructor values, even if the object has been created by using the `setTimestamp()` method. [1] https://3v4l.org/sGEe2 Resolves: #98045 Resolves: #99627 Releases: main, 12.4, 11.5 Change-Id: I095a0b0b376361e25396647d02727ac08f35cae0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83684 Tested-by:
-
- Apr 05, 2024
-
-
Sybille Peters authored
Doctrine dbal function fetchAssociative() was used in combination with accessing an array element without null colesce. Resolves: #103423 Releases: main, 12.4, 11.5 Change-Id: I6f5842f28722dc8b2716533e818fc40ed2fc25ef Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83661 Reviewed-by:
-
- Apr 04, 2024
-
-
Oliver Klee authored
`Console\Helper::strlen()` was deprecated in Symfony 5.3. As we require Symfony >= 5.4, we can safely use the replacement function instead that 12.4 and `main` also use. Note: This already got fixed in main and 12.4 with the upgrade to Symfony 6.1. So this fix here is for 11.5 only. Another note: This change aligns the code with 12.4 and `main`. Changing this to the more fitting `::width()` should happen in a separate later change across versions, not only for 11.5. Resolves: #103503 Related: #98158 Releases: 11.5 Change-Id: Iabd9bf2423501c69e9cd805a6d923f779c8ca04b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83625 Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Jörg Bösche <typo3@joergboesche.de> Reviewed-by:
-
Andreas Kienast authored
In the image editor, the "Cropped area" was configured with a `ceil`ed width and height. Since all other dimensions are `floor`ed, this might cause an overlap. Due to the configured cropping mode, defining that the cropping area must never exceed the image dimensions, the cropper library places the cropper to a position that's mathematically correct but not desired. To solve this issue, the `width` and `height` properties fed to the cropper are now `floor`ed as well, basically aligning with the rest of the coordinates. Resolves: #101520 Releases: main, 12.4, 11.5 Change-Id: I981bd185eaf0db60662a5a6b7b423d84112c2150 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83647 Tested-by:
-
- Mar 23, 2024
-
-
Benjamin Franzke authored
The page tree in TYPO3 v11 and v12 has a default timeout of 300ms for click events to be processed (in order to wait for double-click detection). This caused race conditions in tests since code that waited for #nprogress to hide after clicking on the pagetree did not have anything to wait for (yet), because the progress loaded was only triggered 300ms later, when the click was detected to not be a double click event and the content frame was started to be updated. Also remove wait timeout that were implicitly added for the same issue, but were spread throughout the test cases. Resolves: #103473 Releases: 12.4, 11.5 Change-Id: Ie9c9aff8c8a36581555a9ad352fb98b3d446ba42 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83577 Tested-by:
-
Christian Ludwig authored
Fixes the Doctrine error: Incorrect integer value: '' for column 'editlock' at row 1 Releases: main, 12.4, 11.5 Resolves: #103461 Resolves: #103462 Change-Id: I0e3f0344157f66c07681bd29a47f4f51e32e4225 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83542 Tested-by:
-
- Mar 22, 2024
-
-
Stefan Bürk authored
New core-testing-* images have been build and published in the TYPO3 testing-infrastructure repository and pulled to the core ci gitlab runner instances. [1][2] This change modifies `Build/Scripts/runTests.sh` to set new image version to ensure the usage for all changes based on this change. For information what changed in the image see the patches in the testing-infrastrucure repository linked below. * core-testing-php74 => 2.8 * core-testing-php80 => 2.8 * core-testing-php81 => 2.12 * core-testing-php82 => 1.12 * core-testing-php83 => 1.13 [1] https://git.typo3.org/typo3/CI/testing-infrastructure/-/commit/ebdaefdb54a4fe970abf0cb1d32567bbd6339de5 [2] https://git.typo3.org/typo3/CI/testing-infrastructure/-/commit/21f88537fab0a6c5be866c602f206acdb289a20a Resolves: #103469 Releases: main, 12.4, 11.5 Change-Id: I35ffd10e7979d4fd59aab5a7fa5d52330e71e0e1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83538 Tested-by:
-
- Mar 20, 2024
-
-
Andreas Kienast authored
This commit adds `_ga` to the `excludedParameters` configuration used for the cHash calculation. Resolves: #103435 Releases: main, 12.4, 11.5 Change-Id: I5c79c9264d1d8f09f45db947d714d27b3da4fb00 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83534 Tested-by:
-
- Mar 19, 2024
-
-
Benjamin Franzke authored
* Always clean-up containers when Control-C is pressed * Enforce removing networks even if some containers have not been fully stopped (does not work with older docker versions, therefore only enabled for podman) * Bail out if `waitFor` failed instead of resuming with subsequent commands * Avoid waiting unnecessarily for VNC-web port 7900 in headless mode * Do not derive `--pull=never` from the `$CI` environment variable, as `$CI` is set both in gitlab [1] and github [2] actions. runTests.sh might be used in github actions, therefore this flag is moved into our gitlab-ci specific configuration. * Fix broken `-b podman -s acceptance -d sqlite` UID mapping and sqlite mount Error was: `unknown mount option "uid=1000": invalid mount option` The sqlite tmpfs is removed, as the sqlite tmpfs can not be shared between the PHP development server and codecept (which bootstraps the database in `bin/codecept` in classic-mode) * Avoid `--add-host` for podman for compat with github ubuntu-latest podman version * Fix typos [1] https://docs.gitlab.com/ee/ci/variables/predefined_variables.html [2] https://docs.github.com/en/actions/learn-github-actions/variables#default-environment-variables Resolves: #103420 Releases: main, 12.4, 11.5 Change-Id: Ie8fcdc5ebc5ba651242bb54faffdfd8de0dc6026 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83514 Tested-by:
-
Benjamin Franzke authored
All applicable acceptance tests are now also executed in composer mode. Tests that check classic-mode specific functions are excluded and are therefore now tagged as classic-mode test. The composer mode instance is generated with our CLI setup tools, allowing to mimic the realworld case where a instance is creating via our setup tools instead of from fixtures (which we still use for classic mode tests, but try to reducde/avoid for composer mode tests). The existing existing classic-mode test acceptance test execution will keep running as-is. The v12 backport additionally imports pieces from #102440 as t3editor extension is enabled in this composer-mode, while v12 classic mode is tested (for historic reasons) without t3editor extension enabled. Commands executed: > composer require --dev "typo3/cms-styleguide":"~11.5.5" Resolves: #103297 Releases: main, 12.4, 11.5 Change-Id: I64973f110931b51ed2ef7ef8f8cc3411834fcf37 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83453 Reviewed-by:
-
