[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>
Showing
- typo3/sysext/core/Classes/DataHandling/DataHandler.php 3 additions, 3 deletionstypo3/sysext/core/Classes/DataHandling/DataHandler.php
- typo3/sysext/core/Classes/DataHandling/Localization/DataMapProcessor.php 21 additions, 18 deletions...re/Classes/DataHandling/Localization/DataMapProcessor.php
- typo3/sysext/core/Tests/Functional/DataHandling/IRRE/ForeignField/Modify/DataSet/localizeNCopyPageWSynchronization.csv 7 additions, 8 deletions...ield/Modify/DataSet/localizeNCopyPageWSynchronization.csv
- typo3/sysext/core/Tests/Functional/DataHandling/IRRE/ForeignField/Modify/DataSet/localizePageNAddHotelChildWExclude.csv 5 additions, 3 deletions...eld/Modify/DataSet/localizePageNAddHotelChildWExclude.csv
- typo3/sysext/core/Tests/Functional/Fixtures/Frontend/JsonRenderer.ts 14 additions, 14 deletions...t/core/Tests/Functional/Fixtures/Frontend/JsonRenderer.ts
Please register or sign in to comment