Bug #25131
closed
Localization of child records fails when using MM type relations
100%
Description
Localization of child records doesn't work when using MM as inline relation. Clicking on localize all or when localizing a single child record will remove all default records and show a single empty record or a completely different record.
The problem is even reproducible with irre_tutorial. Make a hotel of type m:n (MM) with two child offers. Now try to localize the hotel and its offers..
Any ideas on how to fix this problem or circumvent it?
https://review.typo3.org/#change,1244
(issue imported from #M17707)
Updated by Bart Dubelaar over 13 years ago
I've done some additional testing:
If I only try to localize a single child record the child is localized correctly but is not added to the parent (no MM record is created). Also the default child is not removed.
If I try to localize all children then only the last child is localized and a load of incorrect MM records are created.
Updated by Oliver Hader over 13 years ago
https://review.typo3.org/#change,1244
Unit tests are available in the irre_turorial:
https://svn.typo3.org/TYPO3v4/Extensions/irre_tutorial/trunk
Updated by Mr. Hudson over 13 years ago
Patch set 3 of change I4c1b7254ff48b592e96c0ac584ab3a79d2b7bfce has been pushed to the review server.
It is available at http://review.typo3.org/1244
Updated by Mr. Hudson over 13 years ago
Patch set 4 of change I4c1b7254ff48b592e96c0ac584ab3a79d2b7bfce has been pushed to the review server.
It is available at http://review.typo3.org/1244
Updated by
Updated by Mr. Hudson over 13 years ago
Patch set 5 of change I4c1b7254ff48b592e96c0ac584ab3a79d2b7bfce has been pushed to the review server.
It is available at http://review.typo3.org/1244
Updated by Mr. Hudson over 13 years ago
Patch set 6 of change I4c1b7254ff48b592e96c0ac584ab3a79d2b7bfce has been pushed to the review server.
It is available at http://review.typo3.org/1244
Updated by Mr. Hudson over 13 years ago
Patch set 1 of change Ia966787037acdb5311ebdb043cdfbd06967da5b0 has been pushed to the review server.
It is available at http://review.typo3.org/1987
Updated by Mr. Hudson over 13 years ago
Patch set 7 of change I4c1b7254ff48b592e96c0ac584ab3a79d2b7bfce has been pushed to the review server.
It is available at http://review.typo3.org/1244
Updated by Mr. Hudson over 13 years ago
Patch set 8 of change I4c1b7254ff48b592e96c0ac584ab3a79d2b7bfce has been pushed to the review server.
It is available at http://review.typo3.org/1244
Updated by Mr. Hudson over 13 years ago
Patch set 9 of change I4c1b7254ff48b592e96c0ac584ab3a79d2b7bfce has been pushed to the review server.
It is available at http://review.typo3.org/1244
Updated by Mr. Hudson over 13 years ago
Patch set 2 of change Ia966787037acdb5311ebdb043cdfbd06967da5b0 has been pushed to the review server.
It is available at http://review.typo3.org/1987
Updated by Mr. Hudson over 13 years ago
Patch set 10 of change I4c1b7254ff48b592e96c0ac584ab3a79d2b7bfce has been pushed to the review server.
It is available at http://review.typo3.org/1244
Updated by Oliver Hader over 13 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset 933254e2e69df05b41ae1f3b026a8f4c6f8fc09d.
Updated by Leo Bossmann over 13 years ago
I have tried to apply above diff in both 4.5.3 and 4.5.4 and it does not resolve the issue.
To me it looks as if this patch does not apply to 4.5 cores, is that true?
Updated by Gerrit Code Review almost 13 years ago
- Status changed from Resolved to Under Review
Patch set 6 for branch TYPO3_4-5 has been pushed to the review server.
It is available at http://review.typo3.org/1987
Updated by Oliver Hader over 12 years ago
- Status changed from Under Review to Resolved
Applied in changeset 1a4150df6666f27557b4e2c6c410ea67b4ed75ff.
Updated by