[TYPO3-mvc] Validation problem: Could not ultimately dispatch the request after ...
Steffen Ritter
info at rs-websystems.de
Wed Dec 30 16:35:52 CET 2009
Michael Knoll schrieb:
> Hello list,
>
> I'm facing a problem concerning object validation. I created an
>
> edit(object1, object2 = NULL)
>
> action in my controller which forwards to an
>
> update(oject1, object2)
>
> action.
>
> When submitting a form without any errors, everything works fine. If I
> input data that does not validate, I get an "Could not ultimately
> dispatch the request after..." exception.
>
> Now I took a look at how ExtBase handles validation errors and I don't
> see a way how this could work in my case.
>
> In the first iteration, Dispatcher::dispatch() tries to run
> updateAction(object1, object2) on my controller. As there are errors
> when validating the objects, a second iteration in
> Dispatcher::dispatch() is triggered via the stop exception.
>
> The referer of the form is correctly determined, in the second
> iteration, the dispatch() function tries to run editAction on my
> controller. But as there are still validation errors in the objects, it
> again raisis errorAction and everything starts from the beginning.
>
> What am I doing wrong? When looking at the blog examples editAction() on
> the blog Controller, everything seems to be exactly the same. How will
> extbase recover from handling with objects that raise an error on
> validation?
>
> I'm thankful for any help!
>
> Greetings
>
> Michael
Hey,
you miss the @dontvalidate annotations at the edit Action, didn't you?
regards
Steffen
More information about the TYPO3-project-typo3v4mvc
mailing list