Values from ext_localconf not active by default

[bittner]

All configuration necessary to activate PHP error and exception logging with Sentry is in ext_localconf.php. Yet still, it's necessary to add those values to LocalConfiguration.php to make the extension work, as described in the README.

It can be shown that the values from ext_localconf.php are indeed loaded successfully and active before an exception occurs. Yet still, the values in LocalConfiguration.php take precedence even though AdditionalConfiguration.php and ext_localconf.php are loaded afterwards, overwriting the handler values in the global array. This seems to be a mannerism (a shortcoming?) of TYPO3, and has been discussed on the TYPO3 #cig-deployment Slack channel.

Be Inspired By Helmut

Jigal von Hemert (on Slack) suggests to take a look at Helmut Hummel's TYPO3-Distribution, which also has its own exception handlers.