[BUGFIX] Flaws in copying a page with localized content elements 06/43906/2
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:51:54 +0000 (12:51 +0200)
commit3eaa2717b3551f2ef1e13d76a46e7d3e1f53fdd9
tree31f9210eb60cf8a7d5b9691fc54f5de7cd5b8459
parent1292b540bb935c318c659e8debce6ff25a67fa25
[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/43906
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