Project

General

Profile

Actions

Bug #81216

closed

Disabled pagetree doesn't survive if e.g. an extension is de-/installed with EM

Added by Josef Glatz about 7 years ago. Updated about 1 month ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2017-05-13
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Problem

The disabled state doesn't survive e.g. an extension de-/installation.

Reproduce with

  1. Open EM
  2. De-/install EM
  3. disabled state is gone

Affected are master and 8-7


Files


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #80621: Show disabled state for navigation component toggle if not availableClosedBenjamin Kott2017-03-31

Actions
Actions #1

Updated by Josef Glatz about 7 years ago

  • Related to Task #80621: Show disabled state for navigation component toggle if not available added
Actions #2

Updated by Josef Glatz about 7 years ago

  • Target version changed from next-patchlevel to Candidate for patchlevel
Actions #3

Updated by Riccardo De Contardi almost 7 years ago

Still an issue with the latest 9.0.0-dev (master)

Steps to reproduce:

1) enter extension manager
1.1) you will see the "disabled" pagetree icon (see the screenshot already attached at this issue)
2) disable an extension

Result:

the pagetree icon is no more in disabled state and is clickable

Expected result:

the pagetree icon still remains disabled, as in extension manager showing the pagtree has no sense.

Actions #4

Updated by Riccardo De Contardi over 6 years ago

Still reproducible in 9.2.0-dev (latest master)

Actions #5

Updated by Riccardo De Contardi over 5 years ago

Still reproducible in 9.5.2-dev (latest master)

Actions #6

Updated by Riccardo De Contardi about 1 month ago

  • Status changed from New to Closed
  • Target version deleted (Candidate for patchlevel)

I close this issue.
Since TYPO3 11 the pageTree hiding has been superseded by a collapsing toggle icon on the side of the Tree itself, which (probably intentionally) doesn't keep state between any backend module and always reverts to being open, to not confuse editors.

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

Actions

Also available in: Atom PDF