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