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