[BUGFIX] l10n_mode=exclude not properly applied when processing ancestors 33/52333/5
authorOliver Hader <oliver@typo3.org>
Mon, 3 Apr 2017 10:58:26 +0000 (12:58 +0200)
committerOliver Hader <oliver.hader@typo3.org>
Mon, 3 Apr 2017 16:27:56 +0000 (18:27 +0200)
commit90d7fd6d6c69553929f1ccde6f22b4fdf618c449
treeb6200e18859569e27ef8b77424169f70315545cd
parent10d623a61062892fc8d7191ccf7edc0c853afcd4
[BUGFIX] l10n_mode=exclude not properly applied when processing ancestors

Fields using l10n_mode=exclude are not properly populated if any ancestor
record is updated.

Change-Id: I0a132191caaac7fbd3642f8a1bc88bb263a127af
Resolves: #80656
Releases: master
Reviewed-on: https://review.typo3.org/52333
Tested-by: TYPO3com <no-reply@typo3.com>
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/Classes/DataHandling/Localization/DataMapProcessor.php
typo3/sysext/core/Tests/Functional/DataHandling/IRRE/ForeignField/Modify/DataSet/localizeNCopyPageWSynchronization.csv
typo3/sysext/core/Tests/Functional/DataHandling/IRRE/ForeignField/Modify/DataSet/localizePageNAddHotelChildWExclude.csv
typo3/sysext/core/Tests/Functional/Fixtures/Frontend/JsonRenderer.ts