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