---
title: "Bugfix: Translating one inline child no longer translates its siblings"
manual: "DeepL Translate (CORE)"
version: "main"
permalink: "https://docs.typo3.org/permalink/web-vision/deepltranslate-core:bugfix-translate-only-the-requested-inline-child-1790949312@main"
source: "Changelog/6.0/Bugfix-TranslateOnlyTheRequestedInlineChild.rst"
rendered: "2026-10-06T14:40:53+00:00"
---

# Bugfix: Translating one inline child no longer translates its siblings {#bugfix-translate-only-the-requested-inline-child-1790949312}

## Description {#description}

Since 6.0.4 and 5.1.7, the DeepL translation of an inline child in connected
mode is handed over to
`\TYPO3\CMS\Core\DataHandling\DataHandler::inlineLocalizeSynchronize()` of
the translated parent, see
[Important: Inline child records are translated through the parent](https://docs.typo3.org/permalink/web-vision/deepltranslate-core:important-inline-child-records-are-translated-through-their-parent-1785623102@main).

The command was sent with the action `localize` and the uid of the child in
`ids`. TYPO3 treats the two as alternatives: with an action, it localizes every
child of the parent field without a translation and ignores `ids`. Only `ids`
without an action localizes the given children, which is what the localize
button of a single inline record in TYPO3 sends.

So translating one inline child with DeepL, for example a card added to an
already translated card group, translated all untranslated children of the same
parent as well. Their content was sent to DeepL and billed.

The command now contains `ids` only.

## Impact {#impact}

Exactly the requested inline child is translated. Other children of the same
parent without a translation stay untranslated until they are translated
themselves.

See pull request [#672](https://github.com/web-vision/deepltranslate-core/pull/672).