Content elements inside already translated b13/container containers are not shown in Localizations Modal Wizard

[achimfritz]

Hi,

having a already translated container and create a new CE in the default-language container

now try to translate ends in an 400 server error (and a frozen modal) during localization wizard (because the CE inside the container "is not found":

this is due the Xclass of EXT:container is overriden in EXT:wv_deepltranslate
correct behaviour (like in the xclass of the EXT:container)

i will provide a pr

s. also:
#44
b13/container#188

Tested with TYPO3 10.4.26, EXT:container 1.5, EXT:wv_deepltranslate 2.0.1

[webworker-united]

I noticed that there is another problem associated with this reported bug:

When changing the translation mode to " Free mode" in the Site Configuration, the translated content is still displayed in the default language.

This applies to all content in a container from the Ext "container".

[webworker-united]

I use TYPO3 core 11.5.10, wv_deepltranslate 2.0.1 and container 1.6.0

[dmitryd]

Unfortunately the fix did not work me.

The problem is that wv_deepltranslate uses cmdmap incorrectly: its keys must be table names and the ext passes settings there ($cmdmap['localization']['custom']['mode']). Container extension calls DataHandler::process_cmdmap() for tt_content compltely ignoring everything else in cmdmap (as it should). So wv_deepltranslate simply does not see that it is being called for container children.

There should be a better detection of the custom translation mode.

[dmitryd]

I'll work on a fix for my client but it will be for version 1.1.4.

[dmitryd]

Okay. I built on top of previous PR and target master in mine. Now container children can be localized together with the parent container (just like gridelements did).