Issue Feature Closed

#19069give more debug details in error case

Franz Holzinger 07/07/08, 09:57 updated 06/15/15, 11:07

Description

When an error occurs in an extension then it is very hard to find out the reason of it, because the TYPO3 Core functions give only very few infos about the error. However it would be very necessary and time saving to also get the bug backtrace and the line and file in the code where the error had happend.

E.g. in t3lib_div::getUserObj you have
debug(”ERROR: No class named: “.$class,1);

But you should have also the output of t3lib_div::debug_trail(); and LINE and FILE infos.
Please insert more debug info in such cases!
This would help to save a lot of time wasted otherwise in searching for the reason of such an error message ‘No class named “classname”’ ‘.

(issue imported from #M8911)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.