Bug #82469
closed
Weird localization behavior of records having IRRE tt_content children
0%
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?
Updated by Susanne Moog almost 7 years ago
- Category set to DataHandler aka TCEmain
Updated by Benni Mack over 5 years ago
- Status changed from New to Needs Feedback
Hey Philipp,
we've recently fixed this in TYPO3 v9.. Can you recheck this?
https://git.typo3.org/Packages/TYPO3.CMS.git/commit/20715ad29adfbb370b5ae971d05ee95dca89307c
Thanks.
Benni.
Updated by Benni Mack over 5 years ago
- Related to Bug #87640: Keep language reference for associated l10n_mode=exclude children added
Updated by Susanne Moog over 4 years ago
- Status changed from Needs Feedback to Closed
No feedback for a year, closing the issue now. If this pops up again, please re-open.