Project

General

Profile

Actions
Copy link

Feature #63063

closed

When deactivating an extension with other depending on it, offer to deactivate those as well

Added by Stefan Neufeind about 10 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2014-11-19
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Currently only an error is thrown. But we might to offer deactivating other extensions as well (recursively).

Layout for that might imho be similar to the "I know what I'm doing"-dialog when installing an ext and the version-deps are not me.

Actions
Copy link
 #1

Updated by Riccardo De Contardi about 9 years ago

  • Target version set to 8 LTS
Actions
Copy link
 #2

Updated by Riccardo De Contardi over 7 years ago

  • Target version changed from 8 LTS to 9.0
Actions
Copy link
 #3

Updated by Susanne Moog almost 7 years ago

  • Target version deleted (9.0)
Actions
Copy link
 #4

Updated by Christian Kuhn over 2 years ago

  • Status changed from New to Closed

Hey.
I hope it's ok to close here: non-composer installations are more-and-more old fashioned and with v11 composer typo3-extensions are also always loaded, effectively handing dependency details over to composer. Non-composer installations should still deal with the "can not unload, please unload something else before" dialog instead, since it is unlikely, this will still be changed.

Actions
Copy link

Also available in: Atom PDF