Skip to content

Child content not rendered in translated containers with "Strict Mode" language handling #626

Open

Description

@lilu82

When using TYPO3's "Strict Mode" for language configuration (fallbacks: strict), child content elements inside a translated container element are not rendered in the frontend. The backend preview appears correct.

The issue seems to be caused by a condition in the Classes/Domain/Factory/FrontendContainerFactory.php that incorrectly checks the language overlay type.

Environment:
TYPO3 Version: 12.4.36
b13/container Version: 3.1.10

The following condition seems to be the cause:

if ($languageAspect->getOverlayType() === LanguageAspect::OVERLAYS_OFF && $record['l18n_parent'] > 0) {
    // This part of the WHERE clause is not added, causing children to be omitted.
    $conf['where'] .= ' OR tx_container_parent=' . $record['l18n_parent'];
}

When debugging the values in a frontend request for a translated page, the results are:

  • $languageAspect->getOverlayType() returns the string 'includeFloating'.
  • LanguageAspect::OVERLAYS_OFF is the string 'off'.

Because 'includeFloating' is not equal to 'off', the condition is false, and the part of the SQL query needed to fetch the child elements of the original language container is never added.

Workaround:
As a temporary fix, removing the $languageAspect->getOverlayType() === LanguageAspect::OVERLAYS_OFF part of the if statement resolves the issue and renders the content correctly:

// Temporary Fix
if ($record['l18n_parent'] > 0) {
    $conf['where'] .= ' OR tx_container_parent=' . $record['l18n_parent'];
}

This seems to indicate that the check for the overlay type is either incorrect for "Strict Mode" or no longer necessary.

Activity

  1. achimfritz commented on Feb 10, 2026

    @achimfritz
    Contributor

    Hi @lilu82 ,
    your translated container is in connected mode? right?
    so the tx_container_parent database value should point to the container in the default language
    maybe you have an inconsistent DB?
    you can try the EXT:container commands
    container:integrity
    container:fixContainerParentForConnectedMode

  2. lilu82 commented on Mar 5, 2026

    @lilu82
    Author

    Hi @achimfritz
    I just tested the latest version and the problem still exists. Yes, I am using “connected mode” and fallbackType = strict . Everything looks perfect in the backend.
    I tried the two tasks, but unfortunately they did not solve the problem.

    debug in frontend:
    standard language
    Image

    translation
    Image

  3. achimfritz commented on Mar 14, 2026

    @achimfritz
    Contributor

    Hi @lilu82 , can you give your site-config + a dump of the related content-elements + your container-configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions