[TYPO3-dev] 6.2 Extbase Issue with Fluid link.action and Backend Plugin
g4-lisz at tonarchiv.ch
g4-lisz at tonarchiv.ch
Thu Apr 24 12:35:10 CEST 2014
Hi Alexander,
thank you for the hint!
I set the rewrittenPropertyMapper to 0, but it seems to make things even
worse...
Looks like it doesn't disable the recursive validating. Now I get a
"Allowed memory size of 268435456 bytes exhausted" error. Looks like
something with my Model Class is fishy...
The error comes from ../Validation/PropertyError.php line 75
addErrors(). There, error msg array are merged. So I comment this out
and log the arrays to a file.
After that, I get a "Maximum execution time of 240 seconds exceeded".
And the logfiles is huge, like 6GB!!
Could it be that the new validation can not handle bidirectional
relations properly? I.e. it gets into a infinite loop?
My model is very large, there are about 8 relations to other objects,
which are large. And some of them point back to the "klinik" object.
Here an excerpt of the logfile:
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
(
....
)
How excatly does this validation work, i.e. what and how does it check?
Could it fail because there is some inconsistency in the DB? Does it
check for empty fields where is a @validate NotEmpty notation?
Thank you
Till
On 04/24/2014 08:58 AM, Alexander Bigga wrote:
> Hi Till,
>
> with the new PropertyManager, there are plenty of things to rewrite.
> E.g. the @dontvalidate annotation is now @ignorevalidation.
>
> Isn't it possible to disable it in 6.2 anymore? I'm still in 4.7 and the
> "rewrittenPropertyMapper" is usually disabled here.
>
> In slub_events, I rewrote the code and activated it:
>
> plugin.tx_slubevents {
> features {
> # uncomment the following line to enable the new Property Mapper.
> rewrittenPropertyMapper = 1
> }
> }
>
> What's your features.rewrittenPropertyMapper setting?
>
> Best regards,
>
> Alexander
>
> Am 23.04.2014 22:54, schrieb g4-lisz at tonarchiv.ch:
>> I still couldn't get it to work.
>>
>> It must be some issue with the new PropertyManager.
>>
>> The error is printed in/Mvc/Controller/ActionController.php if
>> $referringRequest = $this->request->getReferringRequest() is NULL.
>>
>> When does this happen?
>>
>> My object "klinik" is valid, because it does work with other actions...
>>
>> Calling an action in TS using bootstrap also stopped working:
>>
>> 5 = LOAD_REGISTER
>> 5.clinicName {
>> cObject = USER
>> cObject {
>> userFunc = tx_extbase_core_bootstrap->run
>> pluginName = Fe_spitalinfo
>> extensionName = Hplusinfo
>> pluginKey = hplusinfo
>> controller = Klinik
>> action = headerName
>> switchableControllerActions {
>> Klinik {
>> 1 = headerName
>> }
>> }
>> }
>>
>> This worked with 4.6. Now I also get the error "An error occurred while
>> trying to call
>> Tx_Hplusinfo_Controller_KlinikController->headerNameAction()".
>> For some reason the PropertyManager doesn't accept the "klinik" object
>> as an argument any more. The URL looks like this:
>> index.php?id=27&tx_hplusinfo_fe_spitalinfo[klinik]=4
>>
>> I have several plugins on the same page. All of them need "klinik" as
>> argument. Could it be a problem if I have two plugins with the same
>> controller but different default actions on the same page?
>>
>> But, again, this worked with T3 4.6
>>
>> I have no idea what to do...
>>
>> Any help would be much appreciated.
>>
>> Till
>>
>>
>>
>> On 04/22/2014 05:09 PM, g4-lisz at tonarchiv.ch wrote:
>>> He there,
>>>
>>> I have an issue with a extbase backend plugin, which had been working
>>> under 4.6.
>>>
>>> My fluid backend List template shows a edit link like this:
>>>
>>> <f:for each="{kliniks}" as="klinik">
>>> ....
>>> <f:link.action action="edit" arguments="{klinik: klinik}">Edit</f:link.action>
>>> </f:for>
>>>
>>> So there's nothing special.
>>>
>>> When I try do edit the "klinik" object, I get this error:
>>> "An error occurred while trying to call
>>> Tx_Hplusinfo_Controller_KlinikController->editAction()."
>>>
>>> Nothing else, so I have no idea where to start with debugging.
>>>
>>> Here is the editAction:
>>> /**
>>> * Displays a form for editing an existing Klinik
>>> *
>>> * @param Tx_Hplusinfo_Domain_Model_Klinik $klinik the Klinik to display
>>> * @return string A form to edit a Klinik
>>> */
>>> public function editAction(Tx_Hplusinfo_Domain_Model_Klinik $klinik) {
>>> $this->view->assign('klinik', $klinik);
>>> }
>>>
>>> When I put function editAction(... klinik = NULL) {...} then there is no
>>> error and I get a empty form. So there must by something wrong with
>>> passing the "klinik" object to the action.
>>> Is there a change in the extbase / fluid API for backend plugins?
>>>
>>> Cheers,
>>> Till
>>>
>>>
>>> _______________________________________________
>>> TYPO3-dev mailing list
>>> TYPO3-dev at lists.typo3.org
>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>> _______________________________________________
>> TYPO3-dev mailing list
>> TYPO3-dev at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>>
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
More information about the TYPO3-dev
mailing list