[!!!][~TASK] Extbase (Configuration): Major rework of the ConfigurationManager
authorBastian Waidelich <bastian@typo3.org>
Mon, 15 Nov 2010 21:55:25 +0000 (21:55 +0000)
committerBastian Waidelich <bastian@typo3.org>
Mon, 15 Nov 2010 21:55:25 +0000 (21:55 +0000)
commit7ced9a0b03af238c8cdfee2f7b377485c4271d46
tree2b602f5c9f84631c99298b2217f6e184d054d119
parentd6ee3dc021d606ba654503e428450d19c094b9cb
[!!!][~TASK] Extbase (Configuration): Major rework of the ConfigurationManager

Configuration of controllers and actions is now stored in a global registry
($GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['extbase']['extensions']). But you
should never access this directly. Instead always retrieve the frameworkConfiguration
from the ConfigurationManager.
Inserting an Extbase plugin is now as simple as:
lib.foo = USER
lib.foo {
  userFunc = tx_extbase_core_bootstrap->run
  extensionName = YourExtension
  pluginName = YourPlugin
}

This is not really a breaking change as it does not change the public API. But it's not unlikely that it changes the behavior of your Extension in case you modified the TypoScript, that is generated by Tx_Extbase_Utility_Extension::configurePlugin().

NOTE: Unit tests of Extbase and Fluid v4 are broken currently. We'll be fixing those asap
typo3/sysext/extbase/Classes/Configuration/AbstractConfigurationManager.php
typo3/sysext/extbase/Classes/Configuration/BackendConfigurationManager.php
typo3/sysext/extbase/Classes/Configuration/FrontendConfigurationManager.php
typo3/sysext/extbase/Classes/MVC/Web/FrontendRequestHandler.php
typo3/sysext/extbase/Classes/MVC/Web/RequestBuilder.php
typo3/sysext/extbase/Classes/Utility/Extension.php