Issue Bug Closed

#110449web_layout view-mode selector missing after switching from a multi-language to a single-language site so backend-users can't switch back to layout-view on that particular site.

Martin Clewing 08/12/26, 12:37 updated 11/04/26, 19:42

Description

The hidden “Layout/Language Comparison”-Select when only one language is available makes it impossible (or at least difficult, see side note at the bottom) to switch back to Layout Mode when you picked Language Comparison on another site which has more than one language and then go back to the site with only one language.

Steps to reproduce

  1. Open a page on a site with more than one configured language in Content > Layout.
  2. Switch the view mode to “Language Comparison”.
  3. Navigate to a page on a site/subtree that has only one configured language.
  4. Observe: The page shows in language comparison-view (though there is noting to compare). The Layout/Language-Comparison mode selector is missing, so there is no menu to switch back to layout view, means: you are stuck on language comparison view which actually shouldn’t be available on that site.

*Environment*
TYPO3 version: 14.3.6
Installation mode: Composer

side note: you CAN go back to layout view by clicking the default language on the upper right corner. Is that intended and the way to go here?

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 5

  1. Georg Ringer commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2026-11-04T14:50:46+00:00" > 11/04/26, 14:50 </span>

    thanks for creating the issue!
    I was not able to reproduce that on latest version, probably with #110041. can you please check if it still fails on latest v14.3? thanks!

  2. Georg Ringer commented and changed status Needs Feedback Closed <span data-processor="relativetime" data-value="2026-11-04T14:52:17+00:00" > 11/04/26, 14:52 </span>

    thanks for creating the issue!
    I was not able to reproduce that on latest version. can you please check if it still fails on latest v14.3? thanks!