Issue Bug Closed

#74533No errors from GeneralUtility::callUserFunction without explicit request

Mathias Brodala 03/09/16, 10:21 updated 10/02/18, 10:26

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.

Reviews 1