Issue Bug Closed

#95426Reloading the backend does not always show the navigation area (page tree)

Michael Schams 10/01/21, 09:33 updated 05/05/26, 12:55

Description

TYPO3 v11.4.0: in all backend modules under Web, when you force a page reload in your browser, TYPO3 draws the content area and after that, the navigation panel opens to show the page tree.

However, go to Web ➜ Template, select a page, and edit an existing template (button: “Edit the whole template record”). The “General” tab shows the template title, constants area, and setup area. If you force a page reload in this view, TYPO3 draws the content are but does not open the navigation panel.

You end up with the following view (missing page tree):

screenshot-20211001-1131.png

Reviews 0

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

Files 1

History 4

  1. Michael Schams changed subject Reloading the backend does not akways show the navigation area (page tree) Reloading the backend does not always show the navigation area (page tree) <span data-processor="relativetime" data-value="2021-10-01T12:50:03+00:00" > 10/01/21, 12:50 </span>

  2. Riccardo De Contardi commented and changed TYPO3 Version 11 13 <span data-processor="relativetime" data-value="2025-08-17T13:04:13+00:00" > 08/17/25, 13:04 </span>

    Oddly, still happens on 14.0.0-dev

    Steps to reproduce (updated):

    1. Site management > TypoScript module
    2. Click on a page with a TS Template (E.g. home)
    3. dropdown: “Edit TypoScript Record“
    4. Click the button “Edit whole TypoScript record“
    5. Click your browser reload button

    Raised version to 13

  3. Riccardo De Contardi commented <span data-processor="relativetime" data-value="2026-05-05T10:08:31+00:00" > 05/05/26, 10:08 </span>

    This does not happen anymore on version 14 and 15 with the steps on my comment 2

  4. Riccardo De Contardi commented and changed status New Closed <span data-processor="relativetime" data-value="2026-05-05T12:55:59+00:00" > 05/05/26, 12:55 </span>

    I close this issue as this has been solved on version 14 and there likely will be no backport (sorry).

    If you think that this is the wrong decision or experience the issue again please reopen it or open a new issue with a reference to this one.
    Thank you.