TYPO3 Core

Bug #87566

Updated by Alexander Schnitzler almost 6 years ago

This one is a bit tricky and best explained by an example. 

 We have the following configuration: 

 <pre><code class="text"> 
 config.tx_extbase.persistence.classes { 
     TYPO3\CMS\Extbase\Domain\Model\BackendUser { 
         mapping { 
             columns { 
                 username.mapOnProperty = userName 
             } 
         } 
     } 
 } 
 </code></pre> 


 and the following one: 

 <pre><code class="text"> 
 config.tx_extbase.persistence.classes { 
     TYPO3\CMS\Beuser\Domain\Model\BackendUser { 
         mapping { 
             columns { 
                 username.mapOnProperty = overridden 
             } 
         } 
     } 
 } 
 </code></pre> 


 It's important to recognize the following heritage: heritage line: 

 <pre><code class="php"> 
 TYPO3\CMS\Beuser\Domain\Model\BackendUser extends TYPO3\CMS\Extbase\Domain\Model\BackendUser 
 </code></pre> 

 The issue: 
 When a datamap is created, the configuration of the child object *TYPO3\CMS\Beuser\Domain\Model\BackendUser* gets merged with the one of *TYPO3\CMS\Extbase\Domain\Model\BackendUser* but in a way that the configuration of the child object does not override the one of the parent. 


 The property of *TYPO3\CMS\Beuser\Domain\Model\BackendUser* being mapped on field username should be *overridden*, instead it's the one of the parent (*userName*). 

 However, adding new columns works just fine.

Back