Bug #56603
closederror #1251315967: Could not determine the child object typ when adding new property to model
0%
Description
When i manualy add a new property yo a model, I get :
#1251315967: Could not determine the child object type.
clearing the cache or manual deleting the Cache in typo3temp does not help.
it only helps when truncating the cf_extbase_reflection table.
working with 6.2beta6
Updated by Thomas Luzat over 10 years ago
I can confirm that behaviour on an even more recent 6.2-dev version after trying to extend the "news" extension as described here:
http://keinerweiss.de/525-die-extbase-extension-news-um-ein-feld-erweitern.html
Two comments might indicate that the problem exists for others, too:
http://keinerweiss.de/525-die-extbase-extension-news-um-ein-feld-erweitern.html/comment-page-1#comment-1482
http://keinerweiss.de/525-die-extbase-extension-news-um-ein-feld-erweitern.html/comment-page-1#comment-2156
It's unclear whether the latter refers to the same problem, but if it does, this would apply to 6.1.7, too.
Updated by Thomas Mammitzsch over 10 years ago
mostly the same problem here on 6.2
adding a new property results in Warning: class_parents(): object or string expected
from DataMapper. Clearing Cache from Backend doesn't help. Truncating cf_extbase_reflection works.
Updated by Fedir RYKHTIK about 10 years ago
The same in 4.5 LTS
Extabse cache cleaning helps :
TRUNCATE tx_extbase_cache_object;
TRUNCATE tx_extbase_cache_object_tags;
TRUNCATE tx_extbase_cache_reflection;
TRUNCATE tx_extbase_cache_reflection_tags;
Updated by Wouter Wolters about 9 years ago
- Description updated (diff)
- Status changed from New to Rejected
This problem has to do with the extbase reflection cache. This needs to be emptied.
Use the clear cache button in the Install Tool.
Updated by Fedir RYKHTIK over 7 years ago
Hello,
Wouter Wolters wrote:
This problem has to do with the extbase reflection cache. This needs to be emptied.
Use the clear cache button in the Install Tool.
Just a word : on one of our sites, this problem is quite regular.
And empty cache helps only for several hours.
Best regards,
Fedir
Updated by Christian Weiske over 7 years ago
Is anyone here using powermail? We see this regularly on sites with powermail enabled.
It turned out to be Ubuntu 16.04's php-igbinary
extension which got installed as dependency to php-redis
. php-igbinary
is outdated and has a subtle bug:
Updated by Christian Weiske about 7 years ago
- Related to Task #81326: Check igbinary version in install tool added
Updated by Tymoteusz Motylewski about 7 years ago
This issue occurs when your domain model misses type hints.
e.g.
you have
protected $name = '';
Instead of:
/** * @var string */ protected $name = '';
After fixing domain model and clearing cache the error goes away (checked with TYPO3 8.7)
Updated by Michael Stucki almost 7 years ago
Christian Weiske wrote:
It turned out to be Ubuntu 16.04's
php-igbinary
extension which got installed as dependency tophp-redis
.php-igbinary
is outdated and has a subtle bug:
Thanks for the hint, Christian!
Just for clarification if anyone is affected by the same issue: The solution is to uninstall the `php-igbinary` package from the server. It was automatically installed together with `php-redis`, but it's not needed and can be removed. Don't forget to restart PHP after removing it!
see also https://review.typo3.org/#/c/54209/