[TYPO3-v4] 4.5 and incompatible extensions
Krystian Szymukowicz
t33k at prolabium.com
Wed Feb 2 21:45:44 CET 2011
W dniu 2011-02-02 21:36, Ernesto Baschny [cron IT] pisze:
> Krystian Szymukowicz schrieb am 02.02.2011 20:12:
>> W dniu 2011-02-02 19:29, Ernesto Baschny [cron IT] wrote:
>>> Hi,
>>>
>>> I would like to maintain a list of extensions which are known to be
>>> "broken" after the 4.5 upgrade. Usually this happens if an extension
>>> relies on XCLASSing some core class which was refactored during the 4.5
>>> development.
>>
>> in rev. 8481 there has been added writelog when clearing the cache.
>>
>> public function clear_cacheCmd($cacheCmd) {
>> $this->BE_USER->writelog(..........
>>
>> But some ext are using 'clear_cacheCmd' from frontend where
>> $this->BE_USER is not initialised or from BE but without properly
>> initialized be user.
>>
>> So we get:
>> Fatal error: Call to a member function writelog() on a non-object
>>
>>
>> As far as I know this issue touch:
>>
>> a) "mm_forum" - the error is in BE (this has been fixed in trunk of
>> mm_forum)
>> b) "comments" - the erorr is in the FE
>
> This seems easy to fix in the Core by adding a check if BE_USER exists.
> Could you report that issue through the bug tracker? Thanks!
sorry - I forgot to mention that it was put into bug tracker
http://bugs.typo3.org/view.php?id=16844
but it was decided that its fault of extensions and not the core.
See the whole story here:
http://lists.typo3.org/pipermail/typo3-dev/2010-December/042219.html
--
grtz
Krystian Szymukowicz
More information about the TYPO3-project-v4
mailing list