Project

General

Profile

Actions

Feature #19069

closed

give more debug details in error case

Added by Franz Holzinger over 16 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2008-07-07
Due date:
% Done:

0%

Estimated time:
PHP Version:
5.1
Tags:
Complexity:
Sprint Focus:

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("<strong>ERROR:</strong> 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)

Actions #1

Updated by Martin Kutschker over 16 years ago

I'm not a big fan of debug() calls in the Core, but of course it makes sense to make the call right if you do it. Though to me a full trail by default seems to be a bit too much.

Actions #2

Updated by Alexander Opitz over 11 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)

As this report is very old, is the handling in newer TYPO3 CMS Versions (like 6.0/6.1) more like you expect it?

Actions #3

Updated by Ingo Renner over 11 years ago

the mentioned "No class named ..." message still exists and is still hard to solve.

Actions #4

Updated by Alexander Opitz over 11 years ago

  • Status changed from Needs Feedback to New
Actions #5

Updated by Benni Mack almost 10 years ago

  • Status changed from New to Needs Feedback

Hey all,

with development mode activated, you get a full backtrace now, as an exception is thrown. so this solves your problem, right?

Actions #6

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF