[TYPO3-v4] 4.5 and incompatible extensions

[Ernesto Baschny [cron IT]]

Sebastian Fischer schrieb am 03.02.2011 09:17:
> On 02.02.2011 22:36, Ernesto Baschny [cron IT] wrote:
>> Krystian Szymukowicz schrieb am 02.02.2011 21:45:
>>>>> 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
>>
>> Thanks for the pointers. I understood the thread and the proposed
>> solutions. Cool to have that fixed in that extensions which used to call
>> the TCEmain methods without a BE_USER (non documented use of the API).
>>
>> Nevertheless, if someone comes up with a patch which restores the old
>> 4.4 behavior of this particular cache clearing procedure (so that old
>> extensions work as before), I wouldn't have anything against it being
>> included in 4.5, since we want to make the transition path to 4.5 as
>> "smooth" as possible.
>>
>> The fix seems to be pretty easy (simply check if BE_USER is available
>> before calling the writelog() method on it). Maybe adding a call to
>> sysLog() in this situation so that we get more awareness of "bad use" of
>> TCEmain.
>>
>> Cheers,
>> Ernesto
>>
> 
> As this information is developer related, why not use the deprecation
> log for that? By that it would be only logged if deprecation logging is
> activated and the syslog is not flooded.

I thought about that, but its not that we are deprecating anything here,
its just a notice about a misuse of the API.

On the other hand, you're right that the deprecation log would be the
first place to look for if any extension is not behaving correctly and
"might break" in future installations, so it's a good choice.

Cheers,
Ernesto