Task #51286

Custom error views should introduce a controller context somehow

Added by Adrian Föder about 8 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2013-08-23
Due date:
% Done:

0%

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

Description

The error views use Fluid's standalone view, resulting in many possibilities to crash, because most Fluid features depend on a controller context to be set.

Just to mention:

  • f:form's @referrer... fields are empty, resulting in consequential errors when using for a login for example [1]
  • any uri/action related stuff with omitted package argument won't work because no package information is present
  • same for f:translate for example

So, as far as I see it, that standalone view should get a (pseudo-) controller context set...

[1]: for the record, such a consequential error could be using $this->request->getReferringRequest() in the onAuthenticationSuccess() method, this again calls $referringRequest->setArguments() with empty, but set values, eventually ending up with TYPO3\Flow\Mvc\Exception\InvalidActionNameException('The action name must not be an empty string.', 1289472991).

No data to display

Also available in: Atom PDF