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: Stefan Bürk <stefan@buerk.tech>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech>

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: core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>

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: core-ci <typo3@b13.com>
Tested-by: Benni Mack <benni@typo3.org>

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: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>

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: core-ci <typo3@b13.com>
Tested-by: Benni Mack <benni@typo3.org>
Reviewed-by: Benni Mack <benni@typo3.org>

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: core-ci <typo3@b13.com>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: Oliver Hader <oliver.hader@typo3.org>

`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: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Simon Schaufelberger <simonschaufi+typo3@gmail.com>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: Simon Schaufelberger <simonschaufi+typo3@gmail.com>
Tested-by: core-ci <typo3@b13.com>

Resolves: #103615
Releases: main, 12.4, 11.5
Change-Id: I11f609625051f7dc6418596229bed49f282bc842
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83759


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Georg Ringer <georg.ringer@gmail.com>
Reviewed-by: Simon Schaufelberger <simonschaufi+typo3@gmail.com>
Tested-by: Georg Ringer <georg.ringer@gmail.com>
Tested-by: Simon Schaufelberger <simonschaufi+typo3@gmail.com>

`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: Andreas Kienast <a.fernandez@scripting-base.de>
Reviewed-by: Oliver Klee <typo3-coding@oliverklee.de>
Reviewed-by: Andreas Kienast <a.fernandez@scripting-base.de>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>

`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 ...

`\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: core-ci <typo3@b13.com>
Tested-by: Garvin Hicking <gh@faktor-e.de>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Garvin Hicking <gh@faktor-e.de>

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: core-ci <typo3@b13.com>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: Stefan Bürk <stefan@buerk.tech>

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: Stefan Bürk <stefan@buerk.tech>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech>

`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: core-ci <typo3@b13.com>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: Oliver Bartsch <bo@cedev.de>
Tested-by: Georg Ringer <georg.ringer@gmail.com>
Reviewed-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: Jörg Bösche <typo3@joergboesche.de>
Reviewed-by: Georg Ringer <georg.ringer@gmail.com>
Reviewed-by: Andreas Kienast <a.fernandez@scripting-base.de>

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: Andreas Kienast <a.fernandez@scripting-base.de>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Andreas Kienast <a.fernandez@scripting-base.de>

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: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

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: core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>

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: Oliver Bartsch <bo@cedev.de>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: Oliver Klee <typo3-coding@oliverklee.de>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Oliver Klee <typo3-coding@oliverklee.de>
Reviewed-by: Oliver Bartsch <bo@cedev.de>
Tested-by: core-ci <typo3@b13.com>

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: Andreas Kienast <a.fernandez@scripting-base.de>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Andreas Kienast <a.fernandez@scripting-base.de>

 * 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: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

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: Benjamin Franzke <ben@bnf.dev>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Benjamin Franzke <ben@bnf.dev>

In #88366, the caches have been renamed, e.g., from `cache_core`
to `core`. Some occurrences of the old names in comments were missed at
that time. This commit streamlines those occurrences to also use
the new names.

Resolves: #103409
Related: #88366
Releases: main, 12.4, 11.5
Change-Id: I69039160b3d3cc5da00d4f3d3e57fce755d22a63
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83476


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>

Resolves: #103385
Releases: main, 12.4, 11.5
Change-Id: Ifd93dfa4049d0d3550d052fa960ae79cc5a27c34
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83466


Tested-by: core-ci <typo3@b13.com>
Tested-by: Georg Ringer <georg.ringer@gmail.com>
Reviewed-by: Georg Ringer <georg.ringer@gmail.com>

Several tests for URI route generation are stricter and assert
that either the whole URI matches, or that at least the `?cHash=`
suffix is applied for the corresponding test permutations.

Besides that, individual URI assertions are streamlined to use
AbstractEnhancerLinkGeneratorTestCase::assertGeneratedUriEquals.

Resolves: #103396
Releases: main, 12.4, 11.5
Change-Id: I65ae10fa2984021da653bac33579feb6d10a6464
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83465


Tested-by: core-ci <typo3@b13.com>
Tested-by: Oliver Hader <oliver.hader@typo3.org>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>

The commit messages line-length is documented as 72 characters. The
commit-msg hook checks for 72 characters now.

Before the hook checked for 74 characters.

Resolves: #103363
Releases: main, 12.4, 11.5
Change-Id: I15138831a73e84f275e85a5cd88f0b33319f9c1c
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83425


Tested-by: Benni Mack <benni@typo3.org>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Benni Mack <benni@typo3.org>

The public URL resolution in lazy loaded TCA forms (e.g. inline records)
is aligned to use the same path resolution mechanism as in PageRender.

Releases: main, 12.4, 11.5
Resolves: #103296
Change-Id: I981af29b34393302c49dd16216f0baa580d60767
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83399


Tested-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

This prevents warnings during rendering and also looks better.

Resolves: #103355
Releases: main, 12.4, 11.5
Change-Id: I0a677f4f1c5ee8253538dd414fe23384ad49b6e9
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83420


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Lina Wolf <112@linawolf.de>
Tested-by: Lina Wolf <112@linawolf.de>

* .gitignore files contain files that are not
  created during rendering
* .editorconfig conatains old styling, there is a
  main .editorconfig with the containing the correct
  styling

Resolves: #103352
Releases: main, 12.4, 11.5
Change-Id: Ic3189d5f10b8e6f8aa8903cd0924a4a4b4fab191
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83415


Reviewed-by: Lina Wolf <112@linawolf.de>
Tested-by: Lina Wolf <112@linawolf.de>
Tested-by: core-ci <typo3@b13.com>

Resolves: #103350
Related: #103304
Releases: main, 12.4, 11.5
Change-Id: I228f946b8bca26b5c334b352ecd48edfd72c620b
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83413


Tested-by: core-ci <typo3@b13.com>
Tested-by: Lina Wolf <112@linawolf.de>
Reviewed-by: Lina Wolf <112@linawolf.de>

With #90418 the container cache has been excluded from the
regular cache-flush-pipeline.
Therefore flushing has been explicitly performed when writing a
new cache entry (with the intent to clean up old cache entries).

Issue is: Cleaning up the entire folder by deleting the folder means
a concurrent request – that is creating the same DI cache as well –
will fail to write the cache when the folder is (re)moved in that
moment.

It turns out this cache-flush is not needed at all, since the cache
identifier is stable for an TYPO3 instance, therefore a pre-flight
flush can be dropped.

Releases: main, 12.4, 11.5
Resolves: #103294
Change-Id: I1267d794291899e2b0d551b1725bd4a3354823bd
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83361


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: Benjamin Franzke <ben@bnf.dev>

* Introduce a guides.xml, the presence of this file
  triggers the new rendering.
* Remove old Settings.cfg, was only used for Sphinx

Attention: Backport needs manual changes to the guides.xml.

Resolves: #103334
Releases: main, 12.4, 11.5
Change-Id: If2086510e19ca5dc682d9ff0e45c545a458bdfc1
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83349


Tested-by: Lina Wolf <112@linawolf.de>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Lina Wolf <112@linawolf.de>

* Introduce a guides.xml, the presence of this file
  triggers the new rendering.
* Remove outdated genindex: not supported anymore
* Remove old Settings.cfg, was only used for Sphinx

Attention: Backport needs manual changes to the guides.xml.

Resolves: #103336
Releases: main, 12.4, 11.5
Change-Id: I31f40444705530a3a9219fde6530cc46f3888df7
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83345


Tested-by: Lina Wolf <112@linawolf.de>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Lina Wolf <112@linawolf.de>

* Introduce a guides.xml, the presence of this file
  triggers the new rendering.
* Remove outdated genindex: not supported anymore
* Remove old Settings.cfg, was only used for Sphinx

Attention: Backport needs manual changes to the guides.xml.

Resolves: #103340
Releases: main, 12.4, 11.5
Change-Id: Id690e98fb30595e36eb6d573c7a03098668222dd
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83343


Tested-by: core-ci <typo3@b13.com>
Tested-by: Lina Wolf <112@linawolf.de>
Reviewed-by: Lina Wolf <112@linawolf.de>

* Introduce a guides.xml, the presence of this file
  triggers the new rendering.
* Remove outdated genindex: not supported anymore
* Remove old Settings.cfg, was only used for Sphinx

Attention: Backport needs manual changes to the guides.xml.

Resolves: #103339
Releases: main, 12.4, 11.5
Change-Id: Ifde54f6d21ae29ba8c3e8543601048cab2469744
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83341


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Lina Wolf <112@linawolf.de>
Tested-by: Lina Wolf <112@linawolf.de>

* Introduce a guides.xml, the presence of this file
  triggers the new rendering.
* Remove outdated genindex: not supported anymore
* Remove old Settings.cfg, was only used for Sphinx

Attention: Backport needs manual changes to the guides.xml.

Resolves: #103342
Releases: main, 12.4, 11.5
Change-Id: I8d29012e8be9e999129d04c5e84d6a531a9a6b28
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83339


Reviewed-by: Lina Wolf <112@linawolf.de>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Lina Wolf <112@linawolf.de>

* Introduce a guides.xml, the presence of this file
  triggers the new rendering.
* Remove outdated genindex: not supported anymore
* Remove old Settings.cfg, was only used for Sphinx

Attention: Backport needs manual changes to the guides.xml.

Resolves: #103338
Releases: main, 12.4, 11.5
Change-Id: Ia5eae156685428c525fd6e3f27b1c8583b64dd84
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83374


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Lina Wolf <112@linawolf.de>
Tested-by: Lina Wolf <112@linawolf.de>

The setting edit-on-github-directory is needed to find the correct
directory in the monorepository.

Resolves: #103325
Releases: main, 12.4, 11.5
Change-Id: I624cc046bfa899a07c25b9db4a6735c0f99775ad
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83333


Tested-by: core-ci <typo3@b13.com>
Tested-by: Lina Wolf <112@linawolf.de>
Reviewed-by: Lina Wolf <112@linawolf.de>

Ensure recuid is always int+ as the underlying
DB field is `unsigned`.

Resolves: #103101
Releases: main, 12.4, 11.5
Change-Id: I8fa06fa40260bffc5b01eedc4207aec150e7c849
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83337


Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: core-ci <typo3@b13.com>

This patch adds the `gbraid` and `wbraid` parameters to the cHash
parameter exclusion list.

Resolves: #103327
Releases: main, 12.4, 11.5
Change-Id: Ife0f7886980812a6082224a6385a4393782f938b
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83335


Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: core-ci <typo3@b13.com>

* Introduce a guides.xml, the presence of this file
  triggers the new rendering.
* Remove superfluous genindex, it is not supported anymore
* Remove old Settings.cfg, was only used for Sphinx
* Resolve issues from former backports

Attention: Backports need manual changes to the guides.xml.

Resolves: #103307
Releases: main, 12.4, 11.5
Change-Id: Ib4aa42b410be84f787f3c0c8fa7481830db06407
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83281


Tested-by: Chris Müller <typo3@krue.ml>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Chris Müller <typo3@krue.ml>
Tested-by: Lina Wolf <112@linawolf.de>
Reviewed-by: Lina Wolf <112@linawolf.de>