[TYPO3-dev] domesticating t3lib_div::debug

Franz Holzinger franz at fholzinger.com
Sat May 3 15:26:40 CEST 2008


Martin Kutschker a écrit :
> Franz Holzinger schrieb:
>> Dmitry Dulepov [typo3] a écrit :
>>> Steffen Kamper wrote:
>>>> as i work much in BE it's very annyoing that any debug message in BE
>>>> destroys the layout, so i patched my BE like this:
>>> I'd rather add cc_debug into core to open debug statements in a new
>>> window. The solution you propose is not bad but not compatible with 100%
>>> of existing extensions.
>>
>> You should better add an API to the core to support several debug
>> extensions.
> 
> But why? I don't get the point of the whole thread. When I debug small
> extensions a plain echo in my own code is enough. Aftre I'm done I
> remove all the stuff.

But this will not be enough for bigger extensions and more complicated
code or with a new developed extension with many bugs in it. It saves
time to be able to leave the debug statements inside of the code which
do not get displayed normally.

> For the FE there is already debugging possible (the TS message stack for
> the admin panel). So maybe the BE could benefit from a special debug
> function. But that is probably tenplate.php related. No need to bloat
> t3lib_div with that.
So the admin panel should provide debug infos.

- Franz




More information about the TYPO3-dev mailing list