[TYPO3-mvc] error: Could not determine the child object type
Martin Kutschker
masi-no at spam-typo3.org
Wed Jul 7 12:32:57 CEST 2010
While the actual error was on your side, Extbase wasn't really helpful IMHO.
The "Could not determine the child object type" talks about a "child object", but why? Not every
member variable (property) is a reference to an object and not every reference is one to a an entity
that may be described as "child" object.
But how to file this on forge, so it can be changed?
A class evaluation tool would be helpful. With GUI and without (an Extbase lint *) to check if the
annotation is present and makes sense.
Masi
* Would also be helpful for FLOW3, I assume.
Am 07.07.2010 11:27, schrieb Thomas Mammitzsch:
> okay found it. I forget an asterisk in the php doc commment for a member field of my FrontendUser
> class. So that seems to mess up reflection.
>
> before:
>
> /*
> * @var integer
> */
> protected $disable;
>
> after:
>
> /**
> * @var integer
> */
> protected $disable;
>
> regards, Thomas
>
>
> Am 06.07.2010 19:50, schrieb Thomas Mammitzsch:
>> hi list,
>>
>> i do a custom query in my repository:
>>
>> /**
>> * find user by optinCode
>> * @param string $optincode
>> * @return Tx_MyExt_Domain_Model_FrontendUser
>> */
>> public function findByOptinCode($optincode) {
>> $query = $this->createQuery();
>> $query->getQuerySettings()->setRespectEnableFields(FALSE);
>> $query->matching(
>> $query->logicalAnd(
>> $query->equals('Optincode', $optincode),
>> $query->equals('deleted', 0)
>> )
>>
>> );
>>
>> return $query->execute();
>> }
>>
>> The right row is fetched from database. But when the result is mapped to
>> the Tx_MyExt_Domain_Model_FrontendUser object i get a "Could not
>> determine the child object type" error. Any ideas?
>>
>> regards, Thomas
>
More information about the TYPO3-project-typo3v4mvc
mailing list