[TYPO3-core] RFC: #10165: FlexForms: wrong mm-relations after copy and localize

[Peter Kuehn [wmdb>]]

Hi yall,

i just wanted to inform you that Gregory in an offlist mailexchange about
http://lists.netfielders.de/pipermail/typo3-english/2009-February/057917.html
confirmed that
"What happend : my records lost their relations... like you said :/".

gRTz
pekue

Peter Kuehn [wmdb] schrieb:
> Hi yall!
> 
> This is a SVN patch request.
> 
> Type: Bugfix
> 
> Bugtracker references: http://bugs.typo3.org/view.php?id=10165
> 
> Branches: TYPO3 4-1, TYPO3 4-2, trunk
> 
> 
> Problem:
> 
> On copy and localize of a record with a FlexfForm that contains a 
> MM-reference field the resulting record points to wrong relations.
> The needed rows in the MM-table are created, but the field uid_local 
> contains the number of relations instead of the uid of the correct 
> target record.
> 
> 
> Solution:
> 
> The comment in copyRecord_flexFormCallBack() says "If references are set 
> for this field, set flag so they can be corrected later (in 
> ->remapListedDBRecords())" but the remaping fails.
> Instead t3lib_loadDBGroup can be used to resolve the values on 
> beforehand. The records are created correctly by process_datamap() 
> afterwards and dont need to be remaped lateron.
> 
> 
> Notes:
> 
> Maybe this ugly beast first showed up in 2006, when Rene wrote mmforeign 
> and was ported from their into the core. I reported it back then under 
> http://bugs.typo3.org/view.php?id=2381 - obviously wrong filed in tx_dam 
> since this happens to all flexforms holding mm-relations.
> Its mentioned as well in the comments to 
> t3lib_TCEmain->remapListedDBRecords_procDBRefs() (line 5019) but imho 
> its better to create the records correctly than to remap them afterwards.
> 
> Today I stuck with it for the third time in two years - I realy hope the 
> diff solves it with no side effects *cantSeeItAnyLonger
> If it does, it solves #2381 as well and is one fifths on the way to 
> finally marry DAM and Templavoila ;)
> 
> 
> gRTz
> pekue
>