[TYPO3-mvc] 6.2: How to debug recursive validation
g4-lisz at tonarchiv.ch
g4-lisz at tonarchiv.ch
Wed Apr 30 17:58:15 CEST 2014
Hi there,
my extension ported from 4.6 gives me a lot of troubles when calling
link.action from fluid.
I wonder if the new validation handles bidirect relations correctly. My
"root" object has a lot of them.
With the new property mapper, I just get a "An error occurred while
trying to call ...action" error.
When I switch off the new property manager, the PHP script consumes too
much memory (over 500MB). This happens in
../Validation/PropertyError.php line 75
on addErrors(). So I guess there could be some infinite loop...
I piped the errors to a file
public function addErrors($errors) {
$this->logger->error(print_r($errors,true));
//$this->errors = array_merge($this->errors, $errors);
}
The file grows to 6GB before i get a PHP timeout (240sec). Its content
looks like this:
Thu, 24 Apr 2014 01:00:50 +0200 [ERROR] request="5358462053fd8"
component="TYPO3.CMS.Extbase.Validation.PropertyError": A
rray
(
[0] => TYPO3\CMS\Extbase\Validation\Error Object
(
[message:protected] => The given subject was empty.
[code:protected] => 1221560718
[arguments:protected] => Array
(
)
[title:protected] =>
)
)
Thu, 24 Apr 2014 01:00:50 +0200 [ERROR] request="5358462053fd8"
component="TYPO3.CMS.Extbase.Validation.PropertyError": A
rray
(
[0] => TYPO3\CMS\Extbase\Validation\Error Object
(
[message:protected] => Value is no object.
[code:protected] => 1241099148
[arguments:protected] => Array
(
)
[title:protected] =>
)
)
million times... and from time to time something like this:
Thu, 24 Apr 2014 01:00:50 +0200 [ERROR] request="5358462053fd8"
component="TYPO3.CMS.Extbase.Validation.PropertyError": A
rray
(
[name] => TYPO3\CMS\Extbase\Validation\PropertyError Object
(
[message:protected] => Validation errors for property "name"
[code:protected] => 1242859509
[propertyName:protected] => name
[errors:protected] => Array
(
)
[logger:protected] => TYPO3\CMS\Core\Log\Logger Object
(
....
)
Please someone tell me how I can solve this issue (with or without new
property manager)...
BR
Till
More information about the TYPO3-project-typo3v4mvc
mailing list