ConfigurationManager implements ConfigurationManagerInterface

Read onlyYes

Extend the ExtbaseConfigurationManager to read YAML configurations.

YAML files are discovered automatically from every active extension's Configuration/Form/<SetName>/ directory (see FormYamlCollectorConfigurator).

Scope: frontend / backend

Internal
Attributes
#[AsAlias]
\TYPO3\CMS\Form\Mvc\Configuration\ConfigurationManagerInterface::class
$public: true

Table of Contents

Interfaces

ConfigurationManagerInterface
Scope: frontend / backend

Methods

__construct()  : mixed
getYamlConfiguration()  : array<string|int, mixed>
Load and parse YAML files for the current rendering context.

Methods

getYamlConfiguration()

Load and parse YAML files for the current rendering context.

public getYamlConfiguration(array<string|int, mixed> $typoScriptSettings, bool $isFrontend[, ServerRequestInterface|null $request = null ]) : array<string|int, mixed>

Files are resolved via auto-discovery: FormYamlCollector scans every active extension's Configuration/Form/<SetName>/ directory and returns all paths sorted by priority.

Legacy TypoScript-based paths from yamlConfigurations are still honoured during the deprecation period (TYPO3 v14.2–v15.0) and merged after the auto-discovered paths.

The following post-processing steps are applied to the merged configuration:

  • Resolve all declared inheritances
  • Remove all keys whose values are NULL
  • Sort by array keys if all keys within a nesting level are numerical
  • Resolve possible TypoScript settings in FE mode
Parameters
$typoScriptSettings : array<string|int, mixed>
$isFrontend : bool
$request : ServerRequestInterface|null = null
Return values
array<string|int, mixed>

        
On this page

Search results