[TYPO3-mvc] Update to 4.3.3. - Extbase Problem ?

[David Effendi]

Hi Jochen,

thanks for your reply. I re-checked the settings of our extbased 
extensions once more and could not find any missing...

We changed the mentioned row in the dispatcher - and now everything 
works like a charm :D

Greetings
David


Am 29.04.2010 09:30, schrieb Jochen Rau:
> Hi David.
>
> On 27.04.10 19:03, David Effendi wrote:
>> we've just updated our T3 Ver. to 4.3.3. and encounter strange Problems
>> with extbase.
>
> Nothing changed in Extbase shipped with 4.3.3.
>
>> This is the exeption:
>> Tx_Extbase_MVC_Controller_AbstractController::injectSettings() must be
>> an array, null given, called in
>> ..../public_html/typo3_src-4.3.3/typo3/sysext/extbase/Classes/Dispatcher.php
>>
>> on line 234 and defined in
>> ..../public_html/typo3_src-4.3.3/typo3/sysext/extbase/Classes/MVC/Controller/AbstractController.php
>>
>> line 151
>>
>> Our first thought was that our extensions are misconfigured - so we
>> checked our plugin.tx_ourExt.settings - but they all were set.
>
> The code in the Dispatcher changed from
>
> $controller->injectSettings(self::$extbaseFrameworkConfiguration['settings']);
>
> $controller->injectSettings(!empty(self::$extbaseFrameworkConfiguration['settings'])
> ? self::$extbaseFrameworkConfiguration['settings'] : array());
>
> Could you please double-check if your settings are available? OTOH
> !empty() should be replaced by is_array(). I have fixed that in trunk now.
>
>> We checked out the latest version of extbase (21.04.2010) - with this
>> version the exeption is not thrown - but all of our plugins do not
>> display anything - as if no templates are defined...
>
> The blank screen is caused by a feature described in
>
> http://forge.typo3.org/issues/show/6840
>
> it is currently implemented in trunk but reverted in the 1.1 branch.
>
>> When we were running 4.3.2 we've updated the extbase in the meantime
>> with the version published on 19.03.2010.
>>
>> We now took this version into our 4.3.3 and everything works fine again.
>>
>> Can anyone confirm these problems?
>
> No, I can't. ;-)
>
> Regards
> Jochen