* Raised version number to 1.3.0beta2
[Packages/TYPO3.CMS.git] / typo3 / sysext / extbase / ChangeLog.txt
1 ChangeLog for Extbase
2 =====================
4 Changes for 1.3.0 Beta 2:
5 ==========================
6 included in TYPO3 4.5.0 Beta 2.
8 This release includes a whole bunch of bugfixes and refactorings, the most important ones listed below.
9 Because the FlashMessages now use t3lib_FlashMessage, TYPO3 4.5 is MANDATORY!
11 The main changes are:
13 * Tx_Extbase_MVC_Controller_FlashMessages now internally uses the
14 t3lib_FlashMessageQueue that has been introduced with TYPO3 4.3.
15 This results in following changes:
16 - flashmessages are now treated globally, not in a per-extension-scope. As soon as you output the messages first, the session will be flushed
17 - a flashmessage is not a simple strings anymore, but consists of
18 message body and (optionally) title & severity.
19 You can specify title and severity like this:
20 $this->flashMessages->add('Your message', 'some title', t3lib_FlashMessage::WARNING);
21 - you can now output flashmessages in backend that were set from other TYPO3 classes
22 - a revised flashmessage ViewHelper allows you to render flashmessages in the style
23 of core flashmessages now (see Fluid changelog)
24 - Resolves #10821
25 * Configuration Manager can now deal with recurring FlexForm Sections (#6067)
26 * Fixed Tx_Extbase_Domain_Model_FrontendUser (and marked the old API as deprecated)
27 * Bugfixes related to Lazy Loading
29 Full Changes for 1.3.0 Beta 2:
30 ==============================
31 [+BUGFIX] Extbase (Persistence): Persistence_Backend::getIdentifierByObject should work with LazyLoadingProxy
32 getIdentifierByObject should check if object is an instance of Tx_Extbase_Persistence_LazyLoadingProxy and should return the
33 identifier of the real object.
34 [+BUGFIX] Extbase (Configuration): slightly tweaked FrontendConfigurationManager (basically replaced explode() by t3lib_div::trimExplode() call)
35 [+TASK] Extbase (Tests): Added some unit tests for Backend- and FrontendConfigurationManager. To be continued
36 [+BUGFIX] Extbase (DomainObject): added default __toString method to Tx_Extbase_DomainObject_AbstractDomainObject. Thanks to Marco Huber. Resolves #8083
37 [+BUGFIX] Extbase (MVC): Fixed UriBuilder for handling LazyLoadingProxy objects as arguments. Resolves #10705
38 [+TASK] Extbase (Object): re-added Tx_Extbase_Object_Manager to gain more backwards compatibility. This class is marked deprecated and will be removed in Extbase 1.5
39 [+BUGFIX] Extbase (Tests): tweaked ObjectContainer tests. Tests are failing deliberately for now
40 The DI implementation has to be rewritten, as discussed.
41 This relates to: #11160
42 [+BUGFIX] Extbase (Domain): fixed (non-breaking) method name for getting usergroup in Tx_Extbase_Domain_Model_FrontendUser. Resolves #11019
43 [+TASK] extbase (ConfigurationManager): Made FrontendConfigurationManager parse recurring sections in flexforms right. Thanks to Franz Koch (resolves #6067)
44 [+BUGFIX] Extbase (Configuration): Slightly tweaked AbstractConfigurationManager
45 [+TASK] Extbase (Tests): Added unit tests for AbstractConfigurationManager
46 Note: the ConfigurationManager now always overrides switchableControllerActions
47 when retrieving configuration for the current plugin. Before that only happened
48 when no extensionName/pluginName was specified.
49 Additionally: It's not possible anymore to specify new controllers in
50 switchableControllerAction configuration. That was the intended behavior.
51 [+TASK] Extbase (Tests): Renamed test files from "*_testcase.php" to "*Test.php"
52 [+TASK] Extbase (Tests): Moving all Tests in "Unit" directory.
53 [+FEATURE] Extbase (MVC): add possibility to output FlashMessageQueue (Resolves #10821)
54 [+TASK] Extbase (Persistence): counting query results does not work with limit constraints (resolves #10956) Tx_Extbase_Persistence_Storage_Typo3DbBackend::getObjectCountByQuery() replaces the SELECT part
55 of a query by COUNT(*) before executing a statement.
56 This did not work as expected in some cases, e.g. the LIMIT constraint was ignored by the count query.
57 [+TASK] Extbase (Persistence): findOneBy*() methods should return NULL if no item was found (Resolves #10958)
58 [+TASK] Extbase (Core): Slightly improved error handling in bootstrap (Resolves #11055)
59 [~TASK] Extbase (Utility): Changed Tx_Extbase_Utility_TypoScript:convertPlainArrayToTypoScriptArray to self::convertPlainArrayToTypoScriptArray. Resolves #10538.
60 [+BUGFIX] Extbase (MVC): UriBuilder: use current plugin if no pluginName has been specified
61 If multiple plugins are found, that are configured to handle the specified action, Extbase
62 will throw an Exception. Now, this only happens if the *current* plugin does not contain
63 the action.
65 Changes for 1.3.0 Beta 1a:
66 ==========================
67 included in TYPO3 4.5.0 Beta 1.
69 Extbase 1.3.0 Beta 1 has a lot new and greatly improved features, and also many bugfixes.
70 The highlights are outlined below, and explained in-depth a little further down.
72 NOTE: This release brings new table definitions, so please visit the install tool or the Extension
73 Manager and update the tables of Extbase.
77 * Dependency Injection
78 * Dispatcher Refactoring & Completely re-done Configuration Manager
79 This means that Tx_Extbase_Dispatcher is now DEPRECATED!
80 Additionally, if you defined the TypoScript setup for a plugin by hand (which you should not),
81 the syntax has changed a bit there.
82 * QueryResult refactoring (needed for Fluid Widgets)
85 Additionally, the following smaller features were implemented:
87 * Configurable plugin namespaces (#8365)
88 * Automatic target page determination (#9121)
89 * Improved resolveView() mechanism
90 * Allowing plugins to be registered as new content element (#10666)
91 * Default Orderings & QuerySettings (#10319)
93 Breaking Changes:
95 * The UriBuilder now uses the current cObject instead of creating a new instance in the constructor. This is a breaking change if you instantiated the UriBuilder in your code. Please use the Extbase ObjectManager or inject the ConfigurationManager manually.
96 * fixed typo in getter and setter of Tx_Extbase_Domain_Model_FrontendUser::lastlogin
97 * Flashmessages now share a scope throughout the extension. Before, every plugin had it's own scope leading to the messages only being output when entering the same plugin again (e.g. redirecting from one plugin to another would never display the messages)
99 Known issues:
101 * The Unit Tests do not fully work again, we will fix that in the next days.
102 * There might be still issues with the support of backend modules, we are working on that!
104 Dependency Injection
105 --------------------
107 Instead of creating objects through t3lib_div::makeInstance, and connecting them together manually,
108 you yan now use Dependency Injection (DI) for that. Let's give an example: If my class "Tx_Foo_Controller_MyController"
109 needs another class "Tx_Foo_Service_LoggingService", it can get an instance of the logging service
110 by Dependency Injection, by specifying the following code:
112 class Tx_Foo_Controller_MyController {
113 protected $loggingService;
115 /**
116 * @param Tx_Foo_Service_LoggingService $loggingService
117 */
118 public function injectLoggingService(Tx_Foo_Service_LoggingService $loggingService) {
119 $this->loggingService = $loggingService;
120 }
121 }
123 The DI container finds that the class "MyController" has an method whose name starts with "inject",
124 and thus passes the logging service to MyController.
125 It is important that you can *only retrieve Singletons* through the inject annotations. If you need
126 to instanciate a prototype object, it is important to *not* use t3lib_div::makeInstance() anymore
127 (as it bypasses the DI container), but instead you need to inject the ObjectManager, and ask it
128 to create your prototype object using the create() method. Example:
130 class Tx_Foo_Controller_MyController {
131 protected $logFile;
133 /**
134 * @param Tx_Extbase_Object_ObjectManagerInterface $objectManager
135 */
136 public function injectObjectManager(Tx_Extbase_Object_ObjectManagerInterface $objectManager) {
137 $this->logFile = $objectManager->create('Tx_Foo_Domain_Model_LogFile');
138 }
139 }
141 In the above example, you have seen that we reference not the concrete implementation *ObjectManager*,
142 but instead the *ObjectManagerInterface*. If a name ends with "...Interface", Extbase DI automatically
143 strips away the "Interface" from the name, and expects to find a concrete implementation of that interface.
144 This is generally a very good practice: For your core classes, you should always reference an *interface*,
145 and let the DI container instanciate the concrete class.
147 Additionally, Extbase DI allows to *replace* certain implementation classes by other classes through
148 configuration in TypoScript. Let's give an example, and then you can see the concept:
150 config.tx_extbase.objects {
151 Tx_Extbase_Persistence_Storage_BackendInterface {
152 className = Tx_Extbase_Persistence_Storage_Typo3DbBackend
153 }
154 }
156 This essentially means to the DI container: "At all places where you encounter a "BackendInterface",
157 you should instanciate the "Typo3DbBackend" class."
159 However, note that this setting can only be configured *globally* right now, it is not possible
160 to override that on a per-extension basis.
162 Generally, the Extbase DI container provides a subset of the functionality of FLOW3's dependency injection.
164 Dispatcher Refactoring & Completely re-done Configuration Manager
165 -----------------------------------------------------------------
167 In the last versions of Extbase, the Dispatcher (Tx_Extbase_Dispatcher) was the main entry point to Extbase.
168 However, as we did not have Dependency Injection at that point, it became really complex and did lots of things
169 which it should not do in the first place. That's why we greatly improved that part. Now, any Extbase extension
170 is invoked using the Tx_Extbase_Core_Bootstrap. Additionally, the TypoScript used for the registration of any
171 Extbase extension has been cleaned up and adjusted:
173 lib.foo = USER
174 lib.foo {
175 userFunc = tx_extbase_core_bootstrap->run
176 extensionName = YourExtension
177 pluginName = YourPlugin
178 }
180 Additionally, you can also override the list of Switchable Controller Actions through TypoScript:
182 lib.foo = USER
183 lib.foo {
184 userFunc = tx_extbase_core_bootstrap->run
185 extensionName = YourExtension
186 pluginName = YourPlugin
187 switchableControllerActions {
188 Standard {
189 1 = action2
190 2 = action3
191 }
192 }
193 }
195 Of course, you cannot call actions which were not defined previously in the plugin; so the Switchable
196 Controller Actions in TypoScript can be only used to shrink the number of actions available.
198 NOTE: If you manually defined the above snippet, notice that there is a NON-BACKWARDS-COMPATIBLE change
199 in there. But you did that at your own risk, as that was never public API ;)
201 If you used Tx_Extbase_Dispatcher before in your own code, it should still work, but it is deprecated.
202 Instead, instead
204 OLD: Tx_Extbase_Dispatcher::getConfigurationManager()
205 NEW: inject Tx_Extbase_Configuration_ConfigurationManagerInterface into your class
207 OLD: Tx_Extbase_Dispatcher::getPersistenceManager()
208 NEW: inject Tx_Extbase_Persistence_ManagerInterface into your class
210 OLD: Tx_Extbase_Dispatcher::getExtbaseFrameworkConfiguration()
211 NEW: inject Tx_Extbase_Configuration_ConfigurationManagerInterface into your class,
212 and call $configurationManager->getConfiguration(Tx_Extbase_Configuration_ConfigurationManagerInterface::CONFIGURATION_TYPE_FRAMEWORK);
213 on the ConfigurationManager.
215 Please note that the Configuration Manager is STILL NO PUBLIC API, and its method signature has also changed.
217 QueryResult refactoring (needed for Fluid Widgets)
218 --------------------------------------------------
220 Before this change, a call of $query->execute() inside a repository immediately executed the query and
221 returned the result as array.
222 Now, queries are executed lazily at the first moment where you really need them. This means that $query->execute()
223 returns an object of type Tx_Extbase_Persistence_QueryResultInterface, which behaves like an array, meaning you
224 can use foreach() to loop over the query result.
225 However, due to an inconsistency of PHP, the array_* methods, and the iteration methods like current(),
226 next(), ... do NOT work on objects which implement ArrayAccess -- that's the reason why the QueryResult
227 refactoring is a breaking change.
229 Now, however, the following is possible:
230 * Return the first query result: $query->execute()->getFirst()
231 * Get the underlying query: $query->execute()->getQuery()
232 * Convert the result to array: $query->execute()->toArray()
234 This change is a prerequisite for Fluid Widgets to work. See the Fluid ChangeLog for details.
237 Configurable Plugin Namespaces
238 ------------------------------
240 By default each Extbase plugin has a unique URI prefix to avoid collisions with other plugins on your website.
241 This so called plugin namespace usually has the format tx_yourextension_yourplugin.
242 With Extbase 1.3 it is possible to override this namespace. This comes in handy if want to interact with 3rd party
243 extensions, for example with tt_news:
245 plugin.tx_yourextension.view.pluginNamespace = tx_ttnews
247 This sets the plugin namespace of all your plugins inside the extension to "tx_ttnews", making it possibl
248 to directly access tt_news parameters in your controller:
250 /**
251 * @param integer $tt_news tt_news Article uid
252 * @return void
253 */
254 public function yourAction($tt_news) {
255 // interact with $tt_news uid
256 }
258 This works with automatic mapping to Domain models too of course:
260 /**
261 * @param Tx_YourExtension_Domain_Model_NewsArticle $tt_news tt_news Article
262 * @return void
263 */
264 public function yourAction(Tx_YourExtension_Domain_Model_NewsArticle $tt_news) {
265 // interact with $tt_news object
266 }
268 You can also override the plugin namespace for a single instance by adding the section <view.pluginNamespace> to your
269 plugin FlexForm.
272 Automatic target page determination
273 -----------------------------------
275 In TYPO3 v5 we won't have the notion of page uids. To accustom developers to this change, we're trying to free you from
276 the need to specify target pages from within your Extension. Of course you can put all your functionality into one fully
277 fledged plugin, then you won't have to deal with target pages as the current page is used by default.
279 But sometimes you want to be able to change the surrounding contents of a special view of your extension (e.g. the
280 subcontent column of a details page). As before you can still specify the target page explicitly like:
282 <f:link.action action="foo" pageUid="123" />
284 With Extbase 1.3 you can also use a new feature called "automatic target page determination". It is disabled by default,
285 but you can enable it with the following TypoScript:
287 plugin.tx_yourextension.view.defaultPid = auto
289 Then Extbase will search the page tree for a plugin that is configured to handle the specified action and you can omit
290 the "pageUid" parameter in your links. Of course, this does not work if you use the same plugin multiple times in your
291 page tree. In this case you can override the default page ID for the respective plugins:
293 plugin.tx_yourextension_yourplugin.view.defaultPid = 123
295 Note: By default this feature is not activated, because that would be a breaking change in some cases
298 Improved resolveView() mechanism
299 --------------------------------
301 Another feature we backported from FLOW3 is the improved view resolving.
302 You can now change the default view implementation *per format* by inserting the following line in your Controller:
304 protected $viewFormatToObjectNameMap = array(
305 'json' => 'Tx_YourExtension_View_JsonView',
306 'html' => 'Tx_YourExtension_View_HtmlView'
307 );
310 Allowing plugins to be registered as new content element
311 --------------------------------------------------------
313 This is done using an additional parameter to Tx_Extbase_Utility_Extension::configurePlugin
314 that allows you to specify the plugin type. Example:
316 Tx_Extbase_Utility_Extension::configurePlugin(
317 $_EXTKEY,
318 'BlogList',
319 array('Blog' => 'index'),
320 array(),
321 Tx_Extbase_Utility_Extension::PLUGIN_TYPE_CONTENT_ELEMENT
322 );
323 (The default value for the pluginType parameter is Tx_Extbase_Utility_Extension::PLUGIN_TYPE_PLUGIN)
325 Default Orderings & QuerySettings
326 ---------------------------------
328 It is now possible to change the default orderings of a repository without you having to modify the query by setting
329 the $defaultOrderings property of your Repository to a non-empty array:
331 protected $defaultOrderings = array(
332 'title' => Tx_Extbase_Persistence_QueryInterface::ORDER_ASCENDING,
333 'date' => 'title' => Tx_Extbase_Persistence_QueryInterface::ORDER_DESCENDING
334 );
336 This will change the default ordering for all queries created by this repository. Of course you can override the
337 ordering by calling $query->setOrderings() in your custom finder method.
339 Besides it's now possible to change the default query settings of a repository. This way you could for instance disable
340 "respect storage pid" for all queries. We added a life-cycle method "initializeObject" to the repository which will be
341 executed as soon as the repository is created. Just override it like the following:
343 public function initializeObject() {
344 $querySettings = $this->objectManager->create('Tx_Extbase_Persistence_Typo3QuerySettings');
345 $querySettings->setRespectStoragePage(FALSE);
346 $this->setDefaultQuerySettings($querySettings);
347 }
349 Of course, QuerySettings can be overridden too in your custom finder method by calling $query->setQuerySettings();
352 Full Changes for 1.3.0 Beta 1a:
353 ===============================
354 [+TASK] Extbase: Re-implement support for BE modules
355 [+FEATURE] Extbase (Utility): Allow plugins to be registered as new content element
356 Added a fifth parameter to Tx_Extbase_Utility_Extension::configurePlugin that allows
357 you to specify the plugin type (currently "list_type" and "CType" are supported).
358 Thanks to Marc Bastian Heinrichs, Rens Admiraal & Franz Koch for your help!
359 Resolves: #10666
360 [+BUGFIX] Extbase (Utility): Added condition to Tx_Extbase_Utility_Extension::getTargetPidByPlugin() in order to only select tt_content entries that are of CType "list". Thanks to Marc Bastian Heinrichs
361 [!!!][~TASK] Extbase (Configuration): Major rework of the ConfigurationManager
362 Configuration of controllers and actions is now stored in a global registry
363 ($GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['extbase']['extensions']). But you
364 should never access this directly. Instead always retrieve the frameworkConfiguration
365 from the ConfigurationManager.
366 Inserting an Extbase plugin is now as simple as:
367 lib.foo = USER
368 lib.foo {
369 userFunc = tx_extbase_core_bootstrap->run
370 extensionName = YourExtension
371 pluginName = YourPlugin
372 }
373 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().
374 NOTE: Unit tests of Extbase and Fluid v4 are broken currently. We'll be fixing those asap
375 [~TAKS] Extbase (MVC): FrontendRequestHandler now retrieves the current cObject through the ConfigurationManager
376 [+BUGFIX] Extbase (MVC): FrontendRequestHandler was refering to $this->frameworkConfiguration which wasn't available
377 [-API] Extbase (MVC): marked Tx_Extbase_MVC_Web_Request::getContentObjectData() deprecated as should retrieve the current cObject through the ConfigurationManager
378 [+TASK] Extbase (MVC): modified the Tx_Extbase_MVC_Web_RequestBuilder so that it's possible to change the action only by specifying the action parameter. Before you had to specify the controller as well, even if it was the default controller
379 [+BUGFIX] Extbase (MVC): Flashmessages now share a scope throughout the extension. Before, every plugin had it's own scope leading to the messages only being output when entering the same plugin again (e.g. redirecting from one plugin to another would never display the messages)
380 [~TASK] Extbase (Core): The Flashmessages now get persisted in the Bootstrap in resetSingletons()
381 [-TASK] Extbase (Core): Removed some commented lines from Bootstrap
382 [FEATURE] Extbase (Object): Make DI Class Mapping configurable through TS
383 It is now possible to configure the Dependency Injection class mapping by specifying:
384 config.tx_extbase.objects.[FullyQualifiedObjectName].className = [NewClassName]
385 This has the effect of effectively replacing [FullyQualifiedObjectName] with
386 [NewClassName].
387 Resolves: #10559
388 [-TASK] Extbase (Utility): Removed two obsolete checks for $GLOBALS['TSFE']->tmpl->setup['tt_content.']['list.']['20.'] in Tx_Extbase_Utility_Extension
389 [~TASK] Extbase: added two doc comments that were missing
390 [+BUGFIX] Extbase (Persistence): Extbase still used PHPs current() on some QueryResults in Persistence/Repository. Replaced these by calls to the getFirst() method of the QueryResult
391 [+TASK] Extbase (Persistence): added a private field to the QueryResult to make the above case easier to debug: When calling current() on an Iterator, PHP returns the first field of that object instead of calling the current() method of the Iterator interface.. With our somewhat pragmatic approach you'll see the warning if you debug the results of current($query->execute())
392 [+BUGFIX] Extbase (Persistence): Replaced two occurrences of Query->count() by Query->execute()->count() to avoid deprecated warnings in the Core
393 [+BUGFIX] Extbase (MVC): view configuration (templateRootPath, ...) has to be set before View::canRender() is called
394 [!!!][+TASK] Extbase (MVC): The UriBuilder now uses the current cObject instead of creating a new instance in the constructor. This is a breaking change if you instantiated the UriBuilder in your code. Please use the Extbase ObjectManager or inject the ConfigurationManager manually.
395 [+BUGFIX] Extbase (Reflection): ReflectionService now uses a cacheIdentifier per Extension. Besides the Bootstrap now resets the ReflectionService after dispatching a request. This resolves #10146
396 [+TASK] Extbase (Configuration): The ConfigurationManager now holds the current cObject. You can retrieve it via ConfigurationManagerInterface::getContentObject()
397 [+BUGFIX] Extbase (Configuration): When loading configuration of other plugins, the context specific configuration (e.g. flexform settings) are no longer merged with the frameworkConfiguration
398 [+BUGFIX] Extbase (MVC): Controllers are no Singletons by default. If a controller contains stateful fields (e.g. $this->settings) this breaks multiple plugins on one page
399 [+TASK] Extbase (Persistence): QuerySettings now also store the storage page id(s). This is required for the upcoming Ajax Widgets
400 [+BUGFIX] Extbase: fixed php warning in Tx_Extbase_Persistence_LazyLoadingProxy when loading the real instance would return NULL. Resolves #10683
401 [+BUGFIX] Extbase: use 3rd parameter = TRUE of t3lib_div::trimExplode to split switchableControllerActionParts from flexform. Thanks to Georg Ringer. Resolves #10688
402 [+TASK] Extbase: Replaced "public static" by "static public" in various places to be CGL conform
403 [+TASK] Extbase: Marked Utitlity_Extension camelCase/underscore helper functions deprecated
404 [+TASK] Extbase: Removed obsolete FIXME comments, whitespace fixes
405 [!!!] Extbase: Reintegrating branch "dispatcher" to trunk. Resolves: #10605
406 Branch history:
407 [+FEATURE] Extbase (Configuration): Extend ConfigurationManager so that it can load configuration of different plugins
408 [+FEATURE] Extbase (Configuration): 1st level cache for ConfigurationManager. Resolves: #10717. Resolves: #10716
409 [+TASK] Extbase: cleaned up Configuration* implementation, replaced t3lib_div::makeInstance() calls
410 Streamlined ConfigurationManager API and enforced its usage throughout the Extbase classes.
411 Replaced all t3lib_div::makeInstance() calls by $objectManager->create()/$objectManager->get() throughout the Extbase classes.
412 Some smaller tweaks and fixes. Resolves: #10655. Resolves: #10712
413 [TASK] Extbase (Object): Make tests work again. Resolves: #10709
414 [TASK] Extbase (Object): Updated autoload.php and emconf. Relates to: #10561
415 [TASK] Extbase (Object): Use typed exceptions. Relates to: #10561
416 [TASK] Extbase (Object): CGL cleanup
417 Additionally, removed support for @inject annotations at methods. Relates to: #10561
418 [TASK] Extbase (Object): Remove getParents. Relates to: #10561
419 [TASK] Extbase (Object): Remove isSingleton. Relates to: #10561
420 [TASK] Extbase (Object): Remove injectExtensionSettings feature. Relates to: #10561
421 [TASK] Extbase (Object): Change namespaces to Tx_Extbase_Object_Container. Relates to: #10561
422 [TASK] Extbase (Object): Add Container to Extbase. Relates to: #10561
423 [+TASK] Extbase (Core): moved Tx_Extbase_Bootstrap to Tx_Extbase_Core_Bootstrap
424 Moving Bootstrap to be compliant with FLOW3
425 Removed obsolete Classes. Resolves: #10704
426 [+TASK] Extbase: Merged current trunk (r2689) with local modifications into dispatcher branch
427 Note: This still needs a cleanup and some fixes (see FIXME comments) before it can be merged back to the trunk. Relates to: #10605. Relates to: #10655
428 [+TASK] Extbase (Configuration): Moved CONFIGURATION_TYPE_* constraints to ConfigurationManagerInterface. Resolves #10604.
429 [~TASK] Extbase (Configuration): The concrete configuration management strategy gets instanciate only once now.
430 [+FEATURE] Extbase (MVC): Decoupled framework settings from Dispatcher.
431 With the new dependency injection feature you can get the Configuration Manager injected by adding the lines
432 protected $configurationManager;
433 public function injectConfigurationManager(Tx_Extbase_Configuration_ConfigurationManagerInterface $configurationManager) {
434 $this->configurationManager = $configurationManager;
435 }
436 You can get various types of configuration invoking
437 $this->configurationManager->getConfiguration(Tx_Extbase_Configuration_ConfigurationManager::CONFIGURATION_TYPE_EXTBASE)
438 where the class constant must be either CONFIGURATION_TYPE_EXTBASE (for Extbase settings), or CONFIGURATION_TYPE_SETTINGS (for the current module/plugin settings), or CONFIGURATION_TYPE_TYPOSCRIPT (for a raw TS array). Resolves #4741.
439 [~TAKS] Extbase: Removed obsolete code.
440 [~TASK] Extbase: Added core patch for mod.php (see previous commit).
441 [+TASK] Extbase: Changed the way a module gets called.
442 - You can now specify a function name to be invoked by mod.php:
443 $TBE_MODULES['_dispatcher'][] = 'Tx_Extbase_Bootstrap->callModule';
444 - This requires a core patch.
445 [~TASK] Extbase: Changed configuration of the RequestHandler class names to TypoScript.
446 - The request handlers can now be registered in TypoScript with the setting:
447 config.tx_extbase.mvc.requestHandlers.[RequestHandlerClassName] = [RequestHandlerClassName].
448 - There are now two RequestHandlers in Extbase: FrontendRequestHandler and BackendRequestHandler. Common functionality is in the AbstractRequestHandler.
449 [+API][+FEATURE] Extbase (Utility): Implemented mechanism to register RequestHandlers.
450 [+TASK] Extbase: Backported Request Handler Resolver.
451 [~TASK] Extbase: Added "deprecated" annotation to Dispatcher.
452 [~TASK] Extbase: Added missing comment.
453 [+BUGFIX] Extbase (Reflection): The ReflectionService now gets injected to the dispatcher. Related to #10146.
454 [+BUGFIX] Extbase (Reflection): Changed the way the Reflection Service and it's cache gets initialized.
455 * Removed check for pre-initialized Reflection Service in the Bootstrap.
456 * Now using a fixed cache key ('ReflectionData').
457 Related to #10146.
458 [~TASK] Extbase: First step of the Dispatcher refactoring.
459 * Added and adapted some Unit Tests.
460 * Moved the Dispatcher to MVC.
461 * Added a backwards compatibility Dispatcher on root level.
462 * Added a Bootstrap class.
463 * Removed all backend module support for now.
464 Related to #7153.
465 [+TASK] Extbase: Added branch for the dispatcher refactoring.
466 [!!!][+BUGFIX] Extbase: fixed typo in getter and setter of Tx_Extbase_Domain_Model_FrontendUser::lastlogin . Thanks to Christian Schwan. Resolves #9345
467 [+FEATURE] Extbase (MVC): Backport possibility to change the view object class name more easily
468 Backported FLOW3s improved resolveView() mechanism. Tx_Fluid_View_TemplateView is still the default implementation, but can be easily changed by setting $defaultViewObjectName in your controller. Besides it's possible to specifying different views depending on the current request format by setting $viewFormatToObjectNameMap.
469 NOTE: If the view can't be rendered, the new template based "NotFoundView" will be created. So instead of the invisible HTML comments of the EmptyView, you'll get a more meaningful error message if the template file could not be found
470 Resolves: #8990
471 [!!!][+FEATURE] Extbase (Persistence): Backport QueryResult from FLOW3
472 Now Query::execute() returns an instance of QueryResultInterface that allows it to modify the query before actually accessing the records that it retrieves. This is required for the upcoming "Fluid widgets" backport (#10568).
473 NOTE: This change is not backwards compatible, if you work with PHPs array_* functions on the query result. To work around this issue, you'll have to convert the query result to an array before by calling the QueryResult::toArray() method. We're planning to add a compatibility mode, but that's not yet implemented.
474 Resolves: #10566
475 [+BUGFIX] Extbase (Object): Minor fix in ObjectManager to make it compatible with PHP 5.2.x
476 Relates to: #9062
477 [+BUGFIX] Extbase (Object): Refactor Object Manager
478 The Object Manager is now at the same location and
479 has the same API as in FLOW3.
480 [+BUGFIX] Extbase: Major cleanups to Dependency Injection and Persistence
481 Now, DI finally works with Persistence, cleaning
482 this greatly up. Additionally, all internal
483 t3lib_div::makeInstance calls have been replaced.
484 Now, dependency injection is actually usable.
485 Additionally, we completely thought over which
486 persistence classes need to be singleton and which
487 should be prototype, leading finally to a
488 coherent design in the persistence layer.
489 [+BUGFIX] Extbase: remove non-used interfaces
490 Removed classes which were not used.
491 Relates to: #9062
492 Resolves: #10585
493 Resolves: #10564
494 * Cleaned up Persistence Backend
495 * Cleaned up QOM Factory
496 [+BUGFIX] Extbase (MVC): Fix arguments object
497 The arguments object is now correctly inheriting from ArrayObject
498 Resolves: #10562
499 [+BUGFIX] Extbase (MVC): Make database connection work again
500 Resolves: #10585
501 [+FEATURE] Extbase (DI): merging DI into trunk. (resolves #10558)
502 [+TASK] Extbase: Undefined identifier in Tx_Extbase_Persistence_Storage_Typo3DbBackend::removeRow
503 Method clearPageCache was given an undefined variable $uid as second parameter.
504 Resolves: #10570
505 [+TASK] Extbase: $query->contains generate incomplete SQL
506 Use FIND_IN_SET instead of a self-constructed query of LIKE statements
507 Resolves: #8959
508 [+BUGFIX] Extbase (Persistence): Removed method createQuery from the QOMFactory. It is neither part of the API nor is it used by Extbase. Resolves #10215
509 [+BUGFIX] Extbase (Property): Minor fix in PHP doc comment
510 Fix the order of @param annotation in Tx_Extbase_Property_Mapper::mapAndValidate()
511 Resolves: #5887
512 [~CONFIGURATION] Extbase (MVC): Changed default value for automatic target page determination
513 The page id gets automatically detected if plugin.tx_extensionname_pluginname.view.defaultPid
514 is an empty string (was "auto" before). This ensures backwards compatibility.
515 Resolves #9121
516 [TASK] Extbase: moved Release Notes to ChangeLog.txt.
517 [+FEATURE] Extbase (MVC): Automatic target page determination
518 you can use the "pageUid" argument of the link.* and uri.* view helpers
519 to link to a different page. That is deprecated though as we won't have
520 the notion of "page uids" in v5. Instead the target page is now determined
521 automatically.
522 If the target page can't be determined because more than one active
523 plugin is capable of handling the action an exception will be thrown.
524 In that case you'll have to define the target page either by using the
525 pageUid argument or - preferably - by setting
526 plugin.tx_extensionname_pluginname.view.defaultPid to a fixed page uid.
527 Note: This feature still has to be documented!
528 Resolves: #9121
529 [+FEATURE] Extbase (MVC): Configurable plugin namespace
530 until now the namespace (aka prefix) of Extbase plugins was
531 fixed (tx_extensionname_pluginname). This is now configurable
532 via TypoScript. Just write:
533 plugin.tx_extensionname_pluginname.view.pluginNamespace = my_custom_namespace
534 to change the prefix for a specific plugin or
535 plugin.tx_extensionname.view.pluginNamespace = my_custom_namespace
536 to change if for the whole extension.
537 Note: This feature still has to be documented!
538 Resolves: #8365
540 Changes for 1.3.0 Alpha 2:
541 ==========================
542 included in TYPO3 4.5.0 Alpha 2.
544 Since the last version, one (possible BREAKING) change happened:
546 * Fixed Extbase Caching Bug.
547 Non-cacheable actions were cached due to the fact that TYPO3s
548 TypoScript condition "GP" does not merge GET & POST vars.
549 Additionally "switchableControllerActions" that were overridden
550 in the plugin flexform were not taken into account.
552 !!! This is a breaking change if you set up your TS configuration
553 of the plugin manually.
555 Full Changes:
556 -------------
558 [!!!][+BUGFIX] Extbase: Fix Extbase Caching Bug (thanks to Bastian Waidelich)
560 [-TASK] Extbase (MVC): removed fallback to current page in AbstractController::redirect() as that's already done within the UriBuilder if $targetPageUid is NULL
563 Changes for 1.3.0 Alpha 1:
564 ==========================
565 included in TYPO3 4.5.0 Alpha 1.
567 Since the last version, the following notable things happened:
569 * All methods trying to find an object by uid now ignore the storagePid. This changes the behavior of argument mapping and the way extbase fetches 1:1 relations. Resolves #5631. You should not experience any negative side-effects of this change, i.e. if your extension worked before, it will definitely after this change. However, it makes the record handling more robust.
570 * Performance improvements in TypoScript::convertTypoScriptArrayToPlainArray. Thanks to Timo Schmidt.
571 * Numerous other bugfixes, see below.
573 Full Changes:
574 -------------
575 [~TASK] Extbase: Raised version number to 1.3.0-devel to reflect the version scheme defined in the wiki. Resolves #9152. Thanks Xavier for pointing to it.
576 [+TASK] Extbase (MVC): cleaned up View implementations and added assign() and assignMultiple() methods to ViewInterface. This resolves #9137
577 [+BUGFIX] Extbase: Fixed a small typo in extension description.
578 [+BUGFIX] Extbase (Persistence): DataMapper now mapps NULL into a property on non-existing related object instead of FALSE. Resolves #8973.
579 [+BUGFIX] Extbase (Reflection): getParentClass() in Tx_Extbase_Reflection_ClassReflection no longer causes a fatal error if no parent class exists. Resolves #8800.
580 [+BUGFIX] Extbase (Utility): Improved performance of TypoScript::convertTypoScriptArrayToPlainArray. Thanks to Timo Schmidt. Resolves #8857.
581 [~TASK] Extbase: Changed state to 'stable'. Resolves #8768.
582 [+BUGFIX] Extbase: Fixed EOL and encoding of several files. Resolves #8876.
583 [+BUGFIX] Extbase (MVC): Fixed a problem where a non-required action argument throwed Exception if it was not found in the Backend. Thanks to Marc Bastian Heinrichs. Resolves #7277.
584 [!!!][+BUGFIX] Extbase (Persistence): All methods trying to find an object by uid now ignores the storagePid. This changes the behavior of argument mapping and the way extbase fetches 1:1 relations. Resolves #5631.
585 [+BUGFIX] Extbase (Persistence): Fixed a problem where localized objects inside an aggregate are not translated. Resolves #8555.
586 [~TASK] Extbase: Removed new lines at the end of php files.
588 RELEASE NOTES of Extbase v1.0.0
589 ===============================
591 This package contains the Extbase Framework for Extensions. You may
592 also want to install the BlogExample (blog_example) to experiment
593 with. This little example extension demonstrates some of the main
594 features of Extbase. The documentation is bundled in a separate
595 extension called doc_extbase. Both, the blog_example and the
596 doc_extbase can downloaded via TER.
598 http://typo3.org/extensions/repository/view/blog_example/current/
599 http://typo3.org/extensions/repository/view/doc_extbase/current/
601 Currently Extbase is in ALPHA state. Do not expect everything in the
602 right place and shape. And keep in mind that the API may change
603 until TYPO3 v4.3beta1 is released.
605 If you have any feature requests or encountered issues regarding
606 this package please use the facilities on forge to report.
608 We are very open to answer your questions. Please use the newsgroup
610 typo3.projects.typo3v4mvc on lists.netfielders.de
612 so other developers can react to your comments and also
613 profit from the postet solutions. Do not contact a member of the
614 development team via private email (or skype, or visits, or ...)
615 until he accepted this channel. We all do coding for Extbase on
616 our sparetime and must handle our regular work load - and don't
617 forget about our families ;-).
619 We hope you have fun with this package!
621 -- Your Extbase Development Team
624 ===========================
625 git log [startRevision]..HEAD --pretty=format:"%s%n%b%n" | grep -v "^$" | grep -v "git-svn-id"
627 Verify that the merge into the Core succeeded:
628 diff -urNw --exclude=".git" --exclude=".svn" -I "@version" ../../../typo3/sysext/extbase/ .