Project

General

Profile

Actions

Bug #25270

closed

add referer / request uri to error mails

Added by Kay Strobach over 13 years ago. Updated almost 10 years ago.

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

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

currently i get error mails like (with TYPO3 internal error logging
functions):

Host: http://www.[host].de/
Extension: Core: Exception handler (WEB)
Severity: 4

Uncaught TYPO3 Exception: Parameter Error: No file or no parameters given. | UnexpectedValueException thrown in file [path]/typo3_src/typo3_src-4.5.2/typo3/sysext/cms/tslib/showpic.php in line 173

Is there anyway to get the referrer in this Mails or the request_uri?

(issue imported from #M17882)

Actions #1

Updated by Christian Nölle over 13 years ago

Can reproduce this as well on numerous 4.5.2 installations.

Actions #2

Updated by Christian Nölle over 13 years ago

Sorry, just got that wrong. This ticket is not about the showpic.php error.... :)

Actions #3

Updated by Kay Strobach over 13 years ago

no i just wanna find the problem.
and to find the wrong inclusion it would be great to have more information.

This way it would be great to have more information like:

referrer
request_uri
stack_trace

having this information the showpic error should be easily found ;) and fixed - but that is a different topic ;)

Actions #4

Updated by Josef F. Glatz (Old User) over 13 years ago

I've didn't know how to get referrer or request_uri..

I didn't know why - but maybe this help:

Till yesterday, 10:24.28 there where many errors with 404-config:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: Configuration Error: 404 page "/html/typo3/errorpages/404_error.shtml" could not be found. | RuntimeException thrown in file /html/typo3/typo3_src-4.5.2/typo3/sysext/cms/tslib/class.tslib_fe.php in line 1489

Yesterday, 10:26:29: I've installed pagenotfoundhandling. After that, there where no changes at TYPO3 config, or extlist. Only the editor did some changes to tt_content in normal cTypes and fce till 13:06.37.

Since yesterday, 17:41.09 I've got also errors in my TYPO3 log like yours:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: Parameter Error: No file or no parameters given. | UnexpectedValueException thrown in file /html/typo3/typo3_src-4.5.2/typo3/sysext/cms/tslib/showpic.php in line 173

Actions #5

Updated by Kay Strobach over 13 years ago

Hello Guys,

thanks for your replies.

I would like to have a format like:
Perhaps other information can be usefull too.

Regards
Kay

Host: http://www.[host].de/ [^]
Extension: Core: Exception handler (WEB)
Severity: 4
Referer : $_SERVER["HTTP_REFERER"]
Request Uri: $_SERVER['REQUEST_URI']

Uncaught TYPO3 Exception: Parameter Error: No file or no parameters given. | UnexpectedValueException thrown in file [path]/typo3_src/typo3_src-4.5.2/typo3/sysext/cms/tslib/showpic.php in line 17

Actions #6

Updated by Steffen Gebert over 13 years ago

You can implement an own Exception handler, which extends ProductionExceptionHandler or DebugExceptionHandler, reads out the deserved information and adds it to the log message (I assume).

Just place the new handler in a tiny extension (or as a file in typo3conf/) and activate it using the options in the Install Tool regarding the Exception Handlers.

Actions #7

Updated by Alexander Opitz about 10 years ago

  • Description updated (diff)
  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.4)?

Actions #8

Updated by Alexander Opitz almost 10 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