[BUG] Backend: Call to undefined method WebVision\Deepltranslate\Core\Override\CommandMapPostProcessingHook::localizeOrCopyToLanguage()

[localhorst]

Describe the bug
When tranlasting multiple content elements in the backend, an ajax requests in the last step of the translate wizard returns 503.

AJAX URL:

https://www.example.com/typo3/ajax/records/localize?token=438d1d96346654a98bdc167c1337d878053fe9f2&pageId=1142&srcLanguageId=0&destLanguageId=1&action=localizedeepl&uidList%5B0%5D=20898&uidList%5B1%5D=21128&uidList%5B2%5D=20895&uidList%5B3%5D=20892&uidList%5B4%5D=20889&uidList%5B5%5D=21036&uidList%5B6%5D=21054&uidList%5B7%5D=21075

503
Oops, an error occurred!
Call to undefined method WebVision\Deepltranslate\Core\Override\CommandMapPostProcessingHook::localizeOrCopyToLanguage()
Request: 991c83683dbee

To Reproduce
Steps to reproduce the behavior:

1. Login to Backend, use the page module.
2. Create a tranlation page
3. Try the translate content button
4. Use translate with Deepl
5. The translation starts, but is stuck in the last step.
6. The aforementioned ajax url retruns a 503 error.
7. Only the first element is translated, the rest stays empty

Expected behavior
All elements should be translated. It works with with other page content on the same site.

TYPO3 Setup

• TYPO3 13.4
• web-vision/wv_deepltranslate: 5.03
• b13/container: 3.1.10
• More extensions: content-defender, mask
• Server: Nginx
• MySQL 10.5
• PHP 8.3
• DeepL paid API
• composer setup

Additional context
Apparently, the extension b13/container version 3.1.10 doesn't have the function localizeOrCopyToLanguage anymore in \B13\Container\Hooks\Datahandler\CommandMapPostProcessingHook.

Everything works fine when I downgrade to b13/container:3.1.9

[sbuerk]

This has been already fixed last week with #467 couple of hours after the container release and you could use diff of the pull-request as composer patch meanwhile.

We cannot release a fix right now, as we prepared to shift some things into a new shared extension deepl_base which still needs some work to be releasable. We are on it and it
should be released all together the next days.

However, thanks for reporting this issue.

[calien666]

Hi @localhorst,
This issue is fixed in the latest release 5.1.0 as mentioned by @sbuerk above. I will close this issue as fixed by #467