Bug #7858
infiniteLoop through failed validation should be stated clear
| Status: | Resolved | Start date: | 2010-05-21 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 100% |
|
| Category: | Extbase: Validation | |||
| Target version: | - | |||
| Has patch: | No | Tags: | ||
| Votes: | 0 |
Description
hey,
concearning "[TYPO3-mvc] Tx_Extbase_MVC_Exception_InfiniteLoop" we should see if we could state clear when an infiniteLoop occurs through failed validation.
the exception is thrown in Dispatcher.php:dispatch() after 101 tries to process the $request.
my idea would be to grab the info of $request->error (Tx_Extbase_MVC_Controller_ArgumentError). as it allready has a nice to read error-message ($request->errors->[argument]->message) and an exception code ($request->errors->[argument]->code) we could use this to build an exception. if we can not determine the type of error occured we can still throw Tx_Extbase_MVC_Exception_InfiniteLoop.
regards, foertel
History
Updated by Claus Due over 1 year ago
- % Done changed from 0 to 100
This should be closed I think. New exception message reads: "Could not ultimately dispatch the request after ' . $dispatchLoopCount . ' iterations. Most probably, a @dontvalidate annotation is missing on re-displaying a form with validation errors." which is nicely informative - tells you that validation caused the problem and where to look for a cause.
Updated by Ingo Pfennigstorf 8 months ago
- Category set to Extbase: Validation
- Status changed from New to Resolved
- Has patch set to No