Content elements in flux container within content_elements of news get lost on translation

[sneopu]

Current Behavior
content (e.g text) inserted into flux multicol element within a extension (e.g news) is lost after translation into another language. Content not in a multicol element get translated correctly.

Expected behavior/output
On translation of a news record also the content in flux multicol elements should get translated

Environment
• TYPO3 version: 9.5.21
• news version: 7.3.1
• flux: 9.4.1

Additional comments
I checked the the database after translation, the reason ist not a wrong colPos, they dont get created.

[sneopu]

The issue exists also in a actual environment.

Environment
• TYPO3 version: 10.4.10
• news version: 8.5.0
• flux: 9.4.2
• test_provider_extension: 1.0.0

[typoworx-de]

I currently even can't use/find the translation mode (TYPO3 9.5, Flux 9.4.2). The Translate-Button and Translate wizard is missing completly for page content-elements. Any clue what could be wrong there?

[NamelessCoder]

Note for posterity: the cause of this problem appears to be that whenever a News record is translated, DataHandler will not dispatch a localize or copyToLanguage command on related records. Instead, it dispatches a new command that creates copies of the tt_content record(s) with an overridden language.

Flux listens for localize or copyToLanguage commands to determine when to cascade commands to child records.

It might be possible to add a case in \FluidTYPO3\Flux\Integration\HookSubscribers\DataHandlerSubscriber::processCmdmap_beforeStart which detects this special case (as it would be an issue anywhere that uses IRRE relations to tt_content, not just in News) and emulates cascading of a localize command on all children of the tt_content record that was copied.