Feature #65774

Add possibility to clear signals or remove a single slot

Added by Timo Webler over 3 years ago. Updated 5 months ago.

Status:
Under Review
Priority:
Should have
Assignee:
Category:
Backend API
Target version:
-
Start date:
2015-03-16
Due date:
% Done:

0%

PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

It is not possible to remove a slot from a signal or completely clear a signal.

We need this to clear signal PackageManagement::packagesMayHaveChanged, to prevent not needed call of the method \TYPO3\CMS\Core\Package\PackageManager::scanAvailablePackages

Another use case is to change a existing slot by an extension.


Related issues

Related to TYPO3 Core - Feature #73474: Disconnect slots from signals Rejected 2016-02-16

History

#1 Updated by Gerrit Code Review over 3 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38038

#2 Updated by Gerrit Code Review about 3 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38038

#3 Updated by Gerrit Code Review almost 3 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46691

#4 Updated by Gerrit Code Review over 2 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46691

#5 Updated by Timo Webler over 2 years ago

Can we close this issue? Duplicated issue? #65774

#6 Updated by Gerrit Code Review about 2 years ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46691

#7 Updated by Benni Mack about 1 year ago

Can you elaborate why you want to remove this functionality? due to performance penalties or a different issue?

AFAIK since TYPO3 v7 and even with TYPO3 v8, this is only used in ExtensionManager and not on every request.

#8 Updated by Timo Webler 5 months ago

  • Assignee changed from Timo Webler to Benni Mack

Benni Mack wrote:

Can you elaborate why you want to remove this functionality? due to performance penalties or a different issue?

AFAIK since TYPO3 v7 and even with TYPO3 v8, this is only used in ExtensionManager and not on every request.

In our set up TYPO3 can not write the the file "PackageStates.php" and we have not all extensions active.
At a later deployment step we remove the not active Extensions, but for that we need to call TYPO3.
AT this point TYPO3 read all Extension and write this changes to the "PackageStates.php".

That's not a bug of version 8. Because at version 8 only active Extension within the "PackageStages.php".

So please close this issue.

Also available in: Atom PDF