#101118Missing translated menu entries if page is loaded via content_from_pid
Description
No description.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 2
History 6
-
David Hedden changed subject
Missing translated menu entries if page is a mount pointMissing translated menu entries if page is loaded via content_from_pid <span data-processor="relativetime" data-value="2023-06-19T13:06:37+00:00" > 06/19/23, 13:06 </span> -
Astrid Haubold changed Related to #101565 <span data-processor="relativetime" data-value="2023-10-15T17:10:28+00:00" > 10/15/23, 17:10 </span>
-
David Hedden commented <span data-processor="relativetime" data-value="2024-04-24T15:25:25+00:00" > 04/24/24, 15:25 </span>
Issue was solved with #97533 for 12.4
-
Benni Mack commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-06T07:58:42+00:00" > 11/06/26, 07:58 </span>Solved with #97533 (TYPO3 v12.0): resolveTranslatedPageId() no longer exists, and content_from_pid no longer replaces the language aspect, so the menu keeps the requested language and its fallback chain. Closing, as the reporter confirmed.
-
Benni Mack changed Related to #97533 <span data-processor="relativetime" data-value="2026-11-06T07:58:46+00:00" > 11/06/26, 07:58 </span>
Problem found in 10.4, but from checking the source code it should be present in newer versions aswell.
If the current shown page is loaded via content_from_pid and a fallback language. Only pages that are also the fallback language are shown in the menu.
This happens because the menu is generated with pages that can have the fallback language uid or the requested language, but the filterMenuPages function filters with a changed context so it filters out the requested language.
https://api.typo3.org/11.5/_typo_script_frontend_controller_8php_source.html#l01282
https://api.typo3.org/11.5/_abstract_menu_content_object_8php_source.html#l01142
In my case a quick fix was reinitializing the language aspect after running getPageAndRootline since this is the only function that still uses resolveTranslatedPageId.
I suspect there could be more Problems off this kind, since the language aspect is not always initialized with a factory but fetched from the context. So in this case it would be wrong and also without the defined fallback chain.