[TYPO3-dev] showpic.php - Uncaught TYPO3 Exception
Helmut Hummel
helmut.hummel at typo3.org
Sun Sep 4 19:34:57 CEST 2011
On 04.09.11 15:12, Thomas "Thasmo" Deinhamer wrote:
> Ernesto Baschny [cron IT] schrieb:
>> A potential solution would be a more user friendy error message in the
>> frontend only, instead of an exception (as exceptions might also be
>> logged, thus flooding the log with "useless" messages).
>
> I guess that would be a much better solution.
Throwing an exception in this place is correct imho and also presents a
nice error message to the user.
But currently it is the case that all exceptions are logged, even
t3lib_error_http_PageNotFoundException messages. If no error special
handler is defined, renaming/ moving pages could fill your log.
So the question is (in general) when exceptions should be logged and
when not. Should they be logged at all?
There's also a clean and easy solution for this, without touching the
core. Implement and configure your own exception handler class and
decide whether to log exceptions or not or decide by exception number
what to do.
Kind regards,
Helmut
--
Helmut Hummel
TYPO3 Security Team Leader, TYPO3 v4 Core Team Member
TYPO3 .... inspiring people to share!
Get involved: typo3.org
More information about the TYPO3-dev
mailing list