Bug #93014
closed
translation for navigation is incomplete in free mode since v9.5.16
0%
Description
We have a multisite typo3 instance with own site configs for each root page, most of them have german as default language and english as second language but for some its the opposite. For the english ones the menu is not showing the complete page tree in free mode, instead its only showing the translated ones.
Our site config for one of the english instances is as follows:
languages:
-
title: English
enabled: true
base: /
typo3Language: default
locale: en_US.UTF-8
iso-639-1: en
navigationTitle: EN
hreflang: ''
direction: ''
flag: gb
languageId: '0'
-
title: German
enabled: true
base: '/de/'
typo3Language: de
locale: de_DE
iso-639-1: de
navigationTitle: DE
hreflang: de-DE
direction: ltr
fallbackType: free
fallbacks: '0'
flag: at
languageId: '2'
the solution was to apply the patch from https://forge.typo3.org/issues/88344 witch is reverted due to regression issues with patch https://forge.typo3.org/issues/89989
I think there should be a patch available which combains both problem solutions.
Updated by Alexander Bohn almost 4 years ago
- Related to Bug #88344: HMENU directory incompatible with free mode added
Updated by Alexander Bohn almost 4 years ago
- Related to Bug #89989: Since v9.5.12 extendToSubpages has no effect for subpages in menus added
Updated by Felix Nagel over 2 years ago
I can confirm this issue for TYPO3 10.4.31 when using TYPO3\CMS\Frontend\DataProcessing\MenuProcessor in directory mode. Patch from #88344 works.
In addition, this issue is problematic when using EXT:workspaces as it breaks the whole preview for translated, versioned pages when a original language parent page is disabled:
An exception occurred while executing 'SELECT FROM `pages` WHERE (`t3ver_oid` = ?) AND (`t3ver_wsid` = ?) AND (`pages`.`deleted` = 0) LIMIT 1' with params [0, 4]: You have an error in your SQL syntax;
Note the missing select fields.
I was not able to reproduce this in TYPO3 11.5.13.
Updated by Benni Mack 12 months ago
- Status changed from New to Needs Feedback
Yes. I think I fixed this somewhere in TYPO3 v11.5.4 or so. Can someone still reproduce this issue with v11 / v12 / main?
Updated by Riccardo De Contardi 6 months ago
- Status changed from Needs Feedback to Closed
I close this issue for lack of feedback since more than 90 days.
If you think that this is the wrong decision or experience the issue again on recent TYPO3 versions (12 or main) please reopen it or open a new issue with a reference to this one.
Thank you