1.. include:: ../../Includes.txt 2 3========================================================= 4Important: #92100 - YAML imports follow declaration order 5========================================================= 6 7See :issue:`92100` 8 9Description 10=========== 11 12Since #78917 various places of TYPO3 can be configured using YAML. It's 13also possible to use `imports` to split larger configurations into logical 14subparts. The `imports` functionality previously imported the configured 15files in the reverse order in which they were configured in the importing 16file. Since it's sometimes important, e.g. when using `imports` in site 17configurations, the import can now be configured to follow the declaration 18order. The files are then imported in the exact same order as they are 19configured in the importing file. Therefore, a new feature toggle 20`yamlImportsFollowDeclarationOrder` is introduced. It defaults to 21`false` for existing installations and to `true` for new installations. 22This means, if you currently rely on the reverse order, nothing changes 23in your existing installation. 24 25Example: 26 27.. code-block:: yaml 28 29 imports: 30 - { resource: "EXT:site/Configuration/SomeFile.yaml" } 31 - { resource: "EXT:site/Configuration/AnotherFile.yaml" } 32 33With `yamlImportsFollowDeclarationOrder` set to `true`: 34 351. :file:`EXT:site/Configuration/SomeFile.yaml` 362. :file:`EXT:site/Configuration/AnotherFile.yaml` 37 38With `yamlImportsFollowDeclarationOrder` set to `false`: 39 401. :file:`EXT:site/Configuration/AnotherFile.yaml` 412. :file:`EXT:site/Configuration/SomeFile.yaml` 42 43.. index:: Backend, ext:core 44