Bug #74533

No errors from GeneralUtility::callUserFunction without explicit request

Added by Mathias Brodala over 5 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Should have
Category:
Miscellaneous
Target version:
Start date:
2016-03-09
Due date:
% Done:

100%

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

Description

Currently trying to call a method of a non existing (not autoloadable) class via `GeneralUtility::callUserFunction()` basically swallows the error (calls debug() in fact) unless the $errorMode parameter was explicitly set to 2.

This happens basically nowhere in the core thus errors like these are hard to catch/find without additional effort.

The $errorMode parameter should be dropped and the exception could be thrown based on @$TYPO3_CONF_VARS['SYS']['displayErrors'] instead. Always throwing an exception for these kind of errors would be preferable though.

Also available in: Atom PDF