TYPO3 Core

This would also help in scenarios where the input form is on a different page as the output plugin, e.g. a search form on the home page, and the result list on a separate page.

Currently extbase executes the search form action on the result list page. This leads to the problem that all the search form plugin settings are not available anymore, breaking the search form output.

Hi Nicole,

Yes, I've tried to perform overrides and partly succeeded with it. But the problem appears in case of object creation and form has 3 or more steps, represented by 3 actions in controller:

->step1()
->step2(MyObject $object)
->step3(MyObject $object)

In such case, if a validation error appears when going from step 2 to step 3, we'll need to redirect to step 2, which expects MyObject to be passed as an argument, and due to a fact, that object is not yet persisted, the UriBuilder fails to create a proper URL, since object has no uid yet.

I see, that it is a limitation of HTTP POST submitted forms - they can't be easily transformed into GET requests (special show-stopper would be submitted file).

The only question, that still remains: is it possible to have different pages for different steps of object creation? Or to be more specific: have different content blocks, which are surrounding plugin?

This surely can be achieved by using FlexForm of a plugin and insert CEs there, but with complex structures and translations it'll become a nightmare.