Feature #9211

Improve ViewHelper exception handling

Added by Bastian Waidelich over 11 years ago. Updated over 10 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Core
Target version:
-
Start date:
2010-08-09
Due date:
% Done:

0%

Estimated time:
Has patch:

Description

Currently, if a ViewHelper throws an exception, we catch that in the corresponding ViewHelperNode and simply output the exception message.
Instead, we should handle the exception depending on the current "context".

E.g. if in production mode, the exception should be silently ignored (and maybe logged instead). In development context, the message should be outputtet but probably with some more informations about the current template etc.

Question: in FLOW3/TYPO3 v5 we already have the notion of contexts. In v4 we don't have that yet AFAIK. Instead we could use the "devIPmask" setting to switch to development context.. Any ideas?


Related issues

Related to TYPO3.Fluid - Bug #9210: imageViewHelper should not throw exceptionRejected2011-10-152011-10-15

Actions
Related to TYPO3.Fluid - Feature #4704: Improve parsing exception messagesNew2009-09-20

Actions
Related to TYPO3 Core - Bug #61861: Frontend throws exception on missing imageClosed2014-09-24

Actions
Has duplicate TYPO3.Fluid - Bug #30935: Catch ViewHelper exceptions and log them in production contextResolvedChristian Müller2011-10-14

Actions
#1

Updated by Sebastian Kurfuerst over 10 years ago

  • Status changed from Accepted to Rejected

Also available in: Atom PDF