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