[BUGFIX] Flaws in copying a page with localized content elements 56/32356/4
authorOliver Hader <oliver@typo3.org>
Mon, 25 Aug 2014 16:00:24 +0000 (18:00 +0200)
committerOliver Hader <oliver.hader@typo3.org>
Thu, 8 Oct 2015 10:47:54 +0000 (12:47 +0200)
commit6b88e9546985d8038f186954f7a925f86e2c7a4b
tree7ae8d0d2306df4b4029a8b0ad9625848ddc65a62
parent73ebbf8ff08798b61f5cde27c97e9fc5f5f2bed4
[BUGFIX] Flaws in copying a page with localized content elements

Copying a page with localized content elements in a workspace
has some flaws. In a workspace a duplicated record will end up
in a new-placeholder and the specific version record.

The tranlation pointer field of the new-placeholder still
contains the unmodified value of the original record, the
specific version record is fine however.

The reason for that is the special handling for cloning a page
in DataHandler. Each record of a particular table is copied in
reverse order. This way, the localization is created earlier
than the record of the default language.

This change is about skipping the direct copyRecord() call for
records that will be processed inside another copyRecord() call
for the record of the default language.

Resolves: #61179
Releases: master, 6.2
Change-Id: I6647b02095343756d3a41b0c0e985b4777429cd8
Reviewed-on: http://review.typo3.org/32356
Reviewed-by: Andreas Wolf <andreas.wolf@typo3.org>
Tested-by: Andreas Wolf <andreas.wolf@typo3.org>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: Oliver Hader <oliver.hader@typo3.org>
typo3/sysext/core/Classes/DataHandling/DataHandler.php
typo3/sysext/core/Tests/Functional/DataHandling/Regular/Modify/DataSet/copyPage.csv
typo3/sysext/workspaces/Tests/Functional/DataHandling/Regular/Modify/DataSet/copyPage.csv
typo3/sysext/workspaces/Tests/Functional/DataHandling/Regular/Publish/DataSet/copyPage.csv
typo3/sysext/workspaces/Tests/Functional/DataHandling/Regular/PublishAll/DataSet/copyPage.csv