Project

General

Profile

Actions

Feature #23384

closed

syslog entries shall have a back trace

Added by Franz Holzinger over 14 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-08-16
Due date:
% Done:

0%

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

Description

I get a syslog entry. But I do not know from where in the code this comes from. I need a back trace to see where this had happened.

The following SQL has been executed:

$query INSERT INTO sys_log
(
userid,
type,
action,
error,
details_nr,
details,
IP,
tstamp,
workspace
) VALUES (
'2',
'5',
'0',
'1',
'0',
'Core: Error handler (FE): PHP Warning: fopen() [<a href=\'function.fopen\'>function.fopen</a>]: Filename cannot be empty in /path/typo3cms/typo3_src-4.3.3/t3lib/class.t3lib_div.php line 5435',
'89.204.153.69',
'1281962442',
'0'
);

Pg60 exec_INSERTquery(sys_log) - #->handleError // class.t3lib_error_errorhandler.php#14196->writeLog // class.t3lib_error_errorhandler.php#14196->exec_INSERTquery

(issue imported from #M15468)

Actions #1

Updated by Mathias Schreiber almost 10 years ago

  • Description updated (diff)
  • Status changed from New to Resolved
  • Target version deleted (0)

added in 7.0 (even configurable) :)

Actions #2

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF