How to effectively debug TYPO3-Fluid-Form for new object?

Question

I have a "normal" Controller for an object called Application. This object has become quite complex and uses ajax-validations and lots of jQuery-functions to validate property-values and so on. Unfortunately, I am occasionally getting errors from the processAction, telling me the necessary param $newApplication is not set.

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1298012500: 
Required argument "newApplication" is not set for 
VENDOR\myExt\Controller\ApplicationController->process

The new application object is being passed from the newAction to the fluid template just like it is shown in the Blog/Post example of the TYPO3-docbase.

Unfortunately, I am stuck finding the reason, why the process action does not get the application object from the form correctly, since it occurs occasionally (getting the error in the logs on a productive system) but I can`t reproduce it on my own testclient, where everything works as expected with different browsers. Also, the form is public, so i think it is not a problem related to accessrights etc.

Any hint on how to effectively debug this situation would be extremely helpful. Thanks in advance, Oliver

Additional info & code :

Claus Due · Accepted Answer

Most likely, you have one of the following problems:

Your controller action requires an object as argument but in your f:form you have not set the object name or it is set to the wrong name.
Your form posts to a controller action in a different plugin but you did not specify the target plugin name, so the request arguments do not get read by the receiving plugin.
You are posting data which cannot be mapped to the right target object type; for example the data may be incomplete or you are posting a object identifier which does not exist.
You redirect somewhere, to an action that requires an argument, but do not include the argument.

Most of these boil down to how you constructed your template. Rule of thumb: keep as many of the form components using the object and property attributes instead of manually crafting your field names.

Debugging $this->request when this failure happens may yield more information such as missing argument values or source action in case redirection happened.

Further information can only be provided if you post your template code (specifically, everything inside and including the f:form tag). FYI, the use of ajax validation may also cause desync between the actual validation requirements and the validation you perform - so a seemingly valid object may not be valid when it gets mapped and validated by your controller. Note that any override you do in your controller may also have an effect on the behavior of for example validation and argument mapping.

EDIT: clearly, from the source code you posted above you are using custom form property names instead of using object property. This will indeed have an effect on controller argument mapping: your fields will be passed as individual post fields, not properties on an object.

How to effectively debug TYPO3-Fluid-Form for new object?

Answers (1)

Related Questions