---
title: "Important: #103451 - Language menu marks default language fallbacks as available"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:important-103451-1793198547"
source: "Changelog/15.0/Important-103451-LanguageMenuMarksDefaultLanguageFallbacksAsAvailable.rst"
typo3-version: "15.0"
typo3-major: 15
type: "important"
issue: 103451
forge: "https://forge.typo3.org/issues/103451"
tags: ["Frontend", "TypoScript", "ext:frontend"]
rendered: "2026-11-14T17:17:53+00:00"
---

# Important: #103451 - Language menu marks default language fallbacks as available {#important-103451-1793198547}

See [forge#103451](https://forge.typo3.org/issues/103451)

## Description {#description}

A language menu, built with `HMENU` and
`special = language` or with the
`\TYPO3\CMS\Frontend\DataProcessing\LanguageMenuProcessor`, now marks a
language as available if the current page is not translated into it, but the
default language is part of its fallback chain (`fallbacks` in the site
configuration).

Such a page is rendered in the default language when it is called in that
language. Before, the language menu still marked the language as not available
(`USERDEF1` and `USERDEF2` item states,
`available` set to `0` by the `LanguageMenuProcessor`), unless
`special.normalWhenNoLanguage` was set. Languages that fell back to
another, translated language were already marked as available, so all fallbacks
are now treated alike.

A language whose fallback chain does not contain the default language is still
marked as not available if neither it nor one of its fallbacks has a page
translation, as such a page is not rendered. The page option "Hide page if no
translation for current language exists" (`l18n_cfg`) keeps marking an
untranslated language as not available.

Language menus that relied on the previous state to hide or disable such
languages need to check for an existing page translation instead.
