Issue Bug Closed

#54576Make Extbase compatible to work with extensions >= TYPO3 4.5

Stefan Froemken 12/23/13, 09:34 updated 05/05/14, 13:53

Description

Hi Core-Team,

in Extbase and maybe in Fluid, too, you have conditions for special Classnames. Here is a sample as done in PersistentObjectConverter:

if (
    class_exists($targetType)
    && is_subclass_of($targetType, 'TYPO3\\CMS\\Extbase\\DomainObject\\AbstractValueObject')
) {

In my extension I have build in TYPO3 4.7 I have following in my domain model class:

class Tx_Telephonedirectory_Domain_Model_Employee extends Tx_Extbase_DomainObject_AbstractEntity {

Because of using “old” classnames in my extension your condition returns FALSE and __identity was NOT deleted from $source-Array and my FE-Search results in:

Exception while property mapping at property path "":The identity property "" is no UID.

I have also tried it with 0

Exception while property mapping at property path "":Object with identity "0" not found.

There are some more conditions in extbase and fluid with such conditions.

Stefan

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.