Bug #21168

Improve the error and exception handling

Added by Oliver Hader about 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Must have
Category:
-
Target version:
-
Start date:
2009-10-01
Due date:
% Done:

0%

TYPO3 Version:
4.3
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Problem:
The new errorhandling in TYPO3 is way too unflexible.
- Errors are "converted" to exceptions. This is not very useful because every php warning will be turned into an exception. and will stop the script execution.
- DIsplayed error break the backend layout and make forms unusable
- Errors and exceptions are only displayed, but there's no build-in possibility to write errors and exception to a log.

Solution(s):
- introduce a new parameter for errors which should be handled by the error handler. The already existing parameter "exceptionalErrors" is used only for the error which should throw exceptions.
- Display the errors as flashmessages in the BE and as TsLog messages in FE (in the adminpanel)
- implement logging of errors and exceptions to the different logging systems TYPO3

Documentation:
http://wiki.typo3.org/index.php/File:Error_and_exception_handling.odt

(issue imported from #M12093)

12093_improved_errorhandling_v9.diff View (23.5 KB) Administrator Admin, 2009-10-12 14:34

0012093_v10.patch View (23.9 KB) Administrator Admin, 2009-10-20 23:33


Related issues

Related to TYPO3 Core - Feature #19336: Add an error and exception handler (backported from FLOW3) Closed 2008-09-16
Related to TYPO3 Core - Bug #21167: The errorhandling can make TYPO3 Backend unusable Closed 2009-10-01
Related to TYPO3 Core - Feature #20735: Improve error handling for tslib_fe->printError and die() Closed 2009-07-07

History

#1 Updated by Rupert Germann about 10 years ago

FYI: committed to trunk rev 6200

Also available in: Atom PDF