Actions
Bug #81333
closedRedirect finisher cancels all finishers that come after
Status:
Closed
Priority:
Won't have this time
Assignee:
Category:
Form Framework
Target version:
-
Start date:
2017-05-24
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
Hey,
while testing some extensions I ran into the problem that not having the redirect finisher listed as the bottom most finisher will cause all finishers that come below it in the list to not execute.
I understand the logic, but think this is a little confusing. Took me some time to figure out why my other finishers were not executing.
Updated by Ralf Zimmermann over 7 years ago
- Status changed from New to Closed
- Assignee set to Jurian Janssen
- Priority changed from -- undefined -- to Won't have this time
- % Done changed from 0 to 100
Thanks for the note.
The behavior is by design but not documented.
I have added a note within the docs:
https://review.typo3.org/#/c/52485/8..9/typo3/sysext/form/Documentation/Concepts/Index.rst
Actions