Issue Feature Closed

#88398MenuProcessor with support for language menus respecting a detailview for a record

Josef Glatz 05/20/19, 13:32 updated 11/13/26, 15:56

Description

Would be nice to have a easy configurable menu configuration where an integrator can setup a language navigation which can also handle e.g. news-detail views or maybe automatic configuration built upon the existing site configuration/routeEnhancer config.

Reviews 0

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

History 3

  1. Josef Glatz changed description category priority Should have Could have <span data-processor="relativetime" data-value="2019-05-21T16:19:56+00:00" > 05/21/19, 16:19 </span>

  2. Benni Mack commented and changed status New Closed <span data-processor="relativetime" data-value="2026-11-13T15:56:34+00:00" > 11/13/26, 15:56 </span>

    Since TYPO3 v9.3 the LanguageMenuProcessor (and HMENU with special = language) keeps the current query arguments via addQueryString, so language menus on detail pages already link to the translated record, with route enhancers resolving the localized slug. If a language entry should be hidden or marked as unavailable when the record itself is not translated, this can be done with a listener for the PSR-14 FilterMenuItemsEvent, as EXT:news does. Closing this issue; feel free to open a new one if a generic, record-aware solution in Core is still needed.