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