Task #91381

Clearly document "final" nature of Redirect finisher

Added by Mathias Brodala 6 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2020-05-13
Due date:
% Done:

0%

TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

It happens quite often that users create form definitions like this:

# ...
finishers:
  -
    identifier: Redirect
    # ...
  -
    identifier: EmailToReceiver
    # ...

Here the EmailToReceiver will never be executed since the Redirect finisher terminates the current (HTTP) request immediately.

We should take some countermeasures to avoid this situation or at least give hints that a form definition like this will not give the expected results:

  • Update the docs to warn about this in the section about finishers in general and for the Redirect finisher in particular
  • Automatically add the Redirect finisher to the end in the form editor GUI and keep it there even on finisher redordering
  • Refactor the code to actually execute the finisher only at the end of the request after all other finishers (this might require new API since 3rd party code will need this too)
  • Show and/or log a warning if such a form is rendered (this covers hand-written form definitions)

Also available in: Atom PDF