Bug #79234
openSpecial Menu "Section Index" in "Backend User Section" are not rendered in the Frontend (TYPO3: 6.2, 7.6, 8.5)
0%
Description
Problem Description¶
"Special Menu" content elements from type "Section Index" in "Backend User Sections" are not rendered in the Frontend.
tested TYPO3 Versions¶
this problem occurs in TYPO3 versions 6.2, 7.6, and 8.5. It was tested in empty typo3 instances.
Section Index CE on "Page"
Section Index CE on "Backend User Section"
Frontend Output normal Page
Frontend Output Backend User Section
Files
Updated by Sebastian Stein over 7 years ago
Updated by Riccardo De Contardi almost 7 years ago
- Category set to Frontend
It seems still present in 9.0.0-dev (latest master).
Moreover, I don't understand why in 9.0.0-dev the section menu CE shows the page itself (the page selected in the backend in the "selected pages" field - this does not happen for 7.6.18)
Updated by Juergen Waelther about 5 years ago
Same Problem with Typo3 8.7.24, PHP 7.2.16
Updated by Riccardo De Contardi over 4 years ago
It is still present on version 10.0.1.0-dev (latest master); please note that the steps to reproduce it are:
1) Create a page, set its type = Backend user Section
2) Put a couple of CE in it, with a headline
3) Create another page (Standard)
4) Create in it a "Section Index" menu content element, select as starting point the page created at point 1)
5) preview the page
Expected result¶
- the menu should be renderered
Actual result¶
The menu CE is empty (it shows just its surrounding <div id="cXXX" class="frame frame-default frame-type-menu_section frame-layout-0">
and the headline, if present.
Updated by Riccardo De Contardi about 4 years ago
Just checked: still present on 10.4.0-dev (latest master)
Updated by Riccardo De Contardi 12 months ago
- TYPO3 Version changed from 7 to 11
- PHP Version changed from 5.6 to 8.1
This is still present on TYPO3 11.5.26. I also tested it on 13.0.0-dev and is still present, too
I raise the TYPO3 version to 11
Updated by Riccardo De Contardi 20 days ago
Can still confirm the issue for 13.1.0-dev