Project

General

Profile

Actions

Bug #27635

closed

Exception Handlers not used if not defined in localconf.php explicitly

Added by Thomas Deinhamer almost 13 years ago. Updated almost 13 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
-
Target version:
Start date:
2011-06-22
Due date:
% Done:

0%

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

Description

If I define this inside an ext_localconf.php inside an extension:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['productionExceptionHandler'] = 'Tx_HypeDebug_ProductionExceptionHandler';

TYPO3 still uses the default production exception handler,
although in the install tool 'Tx_HypeDebug_ProductionExceptionHandler' is set!

It only works if the line is directly
put into the localconf.php file of TYPO3.
(Via Install-Tool or direct edit via FTP.)

Actions #1

Updated by Steffen Gebert almost 13 years ago

  • Status changed from New to Rejected

Yes, that's the way it is. ExceptionHandler has to be loaded pretty early. Wenn using this in extensions, tell the administrator to adjust the ExceptionHandler.

You could try to set $TYPO3_CONF_VARS['SC_OPTIONS']['errors']['exceptionHandler'] to the class name of the ExceptionHandler, but then you override the displayErrors and exceptionalErrors logic. See t3lib/config_default.php.

Steffen

Actions

Also available in: Atom PDF