Bug #82469

Weird localization behavior of records having IRRE tt_content children

Added by Philipp Kitzberger 2 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-09-12
Due date:
% Done:

0%

TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Localizing a news article having one or more IRRE content elements leads to the weird situation that the translated news record then refers to the localized tt_contents on the one hand but additionally to other tt_contents from all over the system.

I was able to reproduce this with on of our customers TYPO3s as well as with a fresh installation using typo3 8.7.4 and news 6.1.0.

With 8.7.3 (before #81915 was fixed) it was actually even worse (deleting all available CEs in the system), but I think there's still an issue with the TYPO3 localization mechanism in version 8.7 LTS.

The l10n_mode that comes with news for that field is 'mergeIfNotBlank' and has been removed without replacement as mentioned here: https://docs.typo3.org/typo3cms/extensions/core/8.7/Changelog/8.6/Breaking-79243-RemoveL10n_modeMergeIfNotBlank.html

As soon as I remove that l10n_mode via

unset($GLOBALS['TCA']['tx_news_domain_model_news']['columns']['content_elements']['l10n_mode']);

it seems to work.

Now, is this a core bug or should news rather introduce a condition depending on the TYPO3_version?

Also available in: Atom PDF