Child-Records not loaded, if Container-Element is linked via CType:shortcut, points to the original language Container and overlays are turned off

[MajPay]

A complex situation and i don't know what the correct behaviour would actually be. Let's try to explain:

Our customer has a free-mode language-setup, so no overlays should be applied.

The content was created in the default language. They inserted a shortcut element in various places and correctly linked a original language container element. Everything fine...

Then they created the translations and the translated shortcuts still point to the original language. TYPO3 does not care about that and would render the wrong-language-content. But if this content is a container, the FrontendContainerFactory will not find the child-elements!

This was introduced in some update (when we created that site a few years ago it worked as the customer expected) in the container-extension.

I can not auto-fix all shortcut elements because in free mode there might not be a relation from between the content elements in the different languages. So i would need to override the Container DataProcessor to spoof the Context.

But i was wondering what your advice on this is because we did not do any special custom stuff, everything pretty much straight forward.

[kevinlieser]

Same here. Just a really simple and straight forward task. Lets say german is default language (sys_language_uid = 0) and english is sys_language_uid = 1.

• Multi-language project with EXT:container
• Child elements in translated contents (sys_language_uid = 1) points with "tx_conainer_parent" to the default language (sys_language_uid = 0)
• so these secondary-language container elements (sys_language_uid = 1) are not able to get included by shortcut element, because the child records cannot get fetched because the "tx_conainer_parent" is always parent container uid of default language (sys_language_uid = 0)

Part of query that get build:

SELECT * FROM tt_content WHERE ((tt_content.pid IN (123)) AND (tx_container_parent=222) ...

tx_container_parent=222 = englisch container element.
The realy childs have the german original uid set in DB, so noch childs get found.

[kevinlieser]

A solution would maybe look like this (see three lines where the comment is):

EXT:container/Classes/Domain/Factory/FrontendContainerFactory.php->buildContainer()

<?php
    public function buildContainer(ContentObjectRenderer $cObj, Context $context, ?int $uid = null): Container
    {
        
        if ($uid === null) {
            $record = $cObj->data;
        } else {
            $records = $cObj->getRecords('tt_content', ['uidInList' => $uid, 'pidInList' => 0]);
            if (empty($records)) {
                throw new Exception('no record ' . $uid, 1734946029);
            }
            $record = $records[0];
        }
        
        // If container is not default language, take UID of default language because stored childs have default language UID as pareent defined
        if($record['sys_language_uid'] != 0) {
            $record['uid'] = $record['l18n_parent'];
        }
        
        if (!$this->tcaRegistry->isContainerElement($record['CType'] ?? '')) {
            throw new Exception('not a container element with uid ' . $uid, 1734946028);
        }
        $conf = ['where' => 'tx_container_parent=' . $record['uid'], 'orderBy' => 'sorting', 'pidInList' => $record['pid'], 'includeRecordsWithoutDefaultTranslation' => true];
        /** @var LanguageAspect $languageAspect */
        $languageAspect = $context->getAspect('language');
        if ($languageAspect->getOverlayType() === LanguageAspect::OVERLAYS_OFF && $record['l18n_parent'] > 0) {
            $conf['where'] .= ' OR tx_container_parent=' . $record['l18n_parent'];
        }
        $childRecords = $cObj->getRecords('tt_content', $conf);
        $childRecords = $this->recordsByColPosKey($childRecords);
        $container = new Container($record, $childRecords, (int)$record['sys_language_uid']);
        return $container;
    }

[kraemer-igroup]

Hi there, I just stumbled upon the same problem using the latest container version 3.2.2. The issue is NOT (only) having relations to the default language. Relations to the translated record in the current language also do not work (= no show in FE).
@kevinlieser I tried your fix - it works if the relation is in the default language, but not for the current language.

I am migrating a v10 project with container 2.3.6 to v13. The shortcuts ("insert records") are pointing to containers in the current language (not the default language). Everything works as expected within the v10 project.
After migrating to v13 with container 3.2.0 (now 3.2.2), shortcuts do not show content of container elements (and FE is not in default language). Normal elements work as expected. fallbackType is strict.

[akiessling]

I just stumbled up on this error as well.
My setup:
Default = DE
Translation = CS
Language Fallback is disabled, fallbackType = strict

Insert records points to a translated container in CS -> no content is shown in the frontend, only the wrapper div from the container is rendered

Changing the reference to the default language record = works
Inserting the 3 lines from @kevinlieser = works

A guard for having "free" containers should probably be added

// If container is not default language, take UID of default language because stored childs have default language UID as pareent defined
if($record['sys_language_uid'] != 0 && $record['l18n_parent'] > 0) {
    $record['uid'] = $record['l18n_parent'];
}