Bug #40888

Add ViewNotFoundException

Added by Karsten Dambekalns over 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Should have
Category:
MVC
Start date:
2012-09-13
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
No
Complexity:

Description

As noted in a comment on https://review.typo3.org/14439 we should not use NotFoundView ourselves anymore. Thus it seems we should add a ViewNotFoundException exception to handle that case.


Related issues

Related to TYPO3.Flow - Feature #39423: Custom Error RenderersResolvedBastian Waidelich2012-12-25

Actions
Related to TYPO3.Flow - Feature #40857: When template is automatically retrieved but not found, a hint about the tried location should be presentResolvedAdrian Föder2012-09-12

Actions
Related to TYPO3.Flow - Feature #42176: Improve resolving of viewResolvedMarc Neuhaus2012-10-19

Actions
Related to TYPO3.Flow - Task #43930: Remove canRender() completely?!Needs FeedbackSebastian Kurfuerst2012-12-12

Actions
#1

Updated by Bastian Waidelich over 8 years ago

  • Status changed from New to Accepted
  • Assignee set to Bastian Waidelich
#2

Updated by Bastian Waidelich about 8 years ago

Unfortunately this is not as easy as it seemed..
If we throw an exception, one can't ignore the template and return content directly from an action.

This should be resolved with #42176 though.

#3

Updated by Gerrit Code Review about 8 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/17072

#4

Updated by Karsten Dambekalns about 8 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF