Bug #19840
closedFlexForms: wrong mm-relations after copy and localize
0%
Description
On copy or 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.
The bug first showed up with Renes extension mmforeign (see: http://bugs.typo3.org/view.php?id=2381) and may have been ported from their into the core.
It may be already a known issue (see comments for t3lib_TCEmain->remapListedDBRecords_procDBRefs()).
Branches: 4_1, 4_2, trunk
(issue imported from #M10165)
Files
Updated by Peter Kuehn almost 16 years ago
added a testing environement and some documentation as requested on typo3-team-core@lists.netfielders.de
Updated by Peter Kuehn almost 16 years ago
added an improved version that avoids a bug that would have been introduced with the first patch.
credits go to www.planet-schule.de for their patience and support
Updated by Peter Kuehn almost 16 years ago
version 1.1.0 of the demo-extension now contains the fix from the latest bug_10165_fix1.diff
Please use these two versions and ignore the ones posted first!
thnx pekue
Updated by Peter Kuehn over 15 years ago
We found out, that the demo extension will not create the correct database contents if you have extCache enabled. This is due to #0010804.
If you want to use the demo-ext and follow the documentation please disable your extCache first.
thnx
pekue
Updated by Oliver Hader over 15 years ago
I've created a new version of the patch that uses the copyRecord_procBasedOnFieldType() method as it is used for non-flexform values.
The trigger $this->registerDBList to remapListedDBRecords() should be set in any case when relationa fields have been found.
Updated by Oliver Hader over 15 years ago
- TYPO3_4-1 (rev. 5420)
- TYPO3_4-2 (rev. 5421)
- Trunk (rev. 5422)