Bug #3795
Arguments in AbstractController are not cleared after forward
| Status: | Resolved | Start date: | 2009-06-29 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | MVC | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 2 | |||
| PHP Version: | Complexity: | |||
| Has patch: | Affected Flow version: |
Description
The arguments object is created in the constructor of the AbstractController class. After a forward the existing controller will be reused (controller is a singleton) and the old arguments object will be used. This leads to strange validation errors for argument mapping.
Associated revisions
- [FIX] FLOW3 (MVC): Arguments are reset on each call to processRequest, fixes #3795
- [FIX] FLOW3 (MVC): Fixed wrong type hints in AbstractController and added the param for redirect arguments
- [+FEAT] FLOW3 (MVC): Implemented a generic error action for the ActionController with automatic forwarding to the referrer action and with storage of errors in the request. Resolves #3790
History
#1 Updated by Christopher Hlubek about 6 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset r2659.
#2 Updated by Karsten Dambekalns about 6 years ago
- Status changed from Resolved to Accepted
- Assigned To set to Karsten Dambekalns
- % Done changed from 100 to 0
The fix in r2659 breaks REST controllers, maybe more. I'll check.
#3 Updated by Karsten Dambekalns about 6 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r2675.