localization with L10N-Manager import of content elements inside container not working

[bh-teufels]

i got error
Localization failed "container is in free mode or not translated"
when i want to translate my content over L10N-Manager Import (from Default DE to EN)

has someone ever had this problem?

excerpt of import xml:

<data table="tt_content" elementUid="118" key="tt_content:NEW/1/118:bodytext" transformations="1"><p>Far far away, behind the word mountains, far from the countries Vokalia and Consonantia, there live the blind texts. Separated they live in Bookmarksgrove right at the coast of the Semantics, a large language ocean. A small river named Duden flows by their place and supplies it with the necessary regelialia. It is a paradisematic country, in which roasted parts of sentences fly into your mouth. Even the all-powerful Pointing has no control about the blind texts it is an almost unorthographic life One day however a small line of blind text by the name of Lorem Ipsum decided to leave for the far World of Grammar.</p>

ContentElement 118 is inside a container with id 117

-> the content element on EN get created but with default text

Typo3 10.4.20
container 1.3.1
l10nmgr 10.1.2

[achimfritz]

Hi @bh-teufels , some time ago i have created a patch for l10nmgr to support EXT:container
can you test https://gitlab.com/achimfritzb13com/l10nmgr/-/tree/feature/container-support is working for you? (then i will create a PR for EXT:l10nmgr)

[bh-teufels]

Hi @achimfritz thank you i will try it.
does it do changes on export too so do i need to create a new export or could i try the import of the file i already have?

[achimfritz]

the patch affects only import.

[achimfritz]

@bh-teufels but i think you have to deleted already imported translations (because they are broken)

[bh-teufels]

yes thank you first try worked well.
we now check the translations and i will give a final feedback

[achimfritz]

@bh-teufels any news?

[bh-teufels]

yes worked very well.
all translations were imported correctly
Thank you very much

[achimfritz]

i have created a PR https://gitlab.com/coderscare/l10nmgr/-/merge_requests/44

[mschwemer]

Thanks Achim for the PR.

I can confirm the issue and that you PR works in the l10nmgrrepo.

Currently we install it via cweagans/composer-patches.

[Bunnyfield]

We just got another issue report today which delivered a screenshot of the error messages involved, which are generated by Container itself.

There is this method

\B13\Container\Hooks\Datahandler\CommandMapBeforeStartHook::processCmdmap_beforeStart

which in turn calls the method

\B13\Container\Hooks\Datahandler\CommandMapBeforeStartHook::unsetInconsistentLocalizeCommands

which is used to check if there are already translated containers when a child element is to be translated.

Since in the case of the L10nmgr a statement can be contained in the same command map for both elements, i.e. parent and child element, the attempt to find a suitable container that has already been translated must of course fail if this container has not been translated before.

The attempt would also fail in the same way for any other use of the command map with a set of multiple and nested elements, regardless of L10nmgr. So IMHO this has to be fixed by Container, because a fix in L10nmgr would just be a workaround.

[bh-teufels]

localizationteam/l10nmgr is for Typo3 v11 released.
Does anybody know if the 11.0.0 Version working with container?
if not @achimfritz is planed to merge your patch with the 11.0.0 version?

Thank you all

[SicorDev]

It seems the patch was already added to l10nmgr, so this issue is done?
CodersCare/l10nmgr@0f01dd3

[achimfritz]

should be done