Feature #65774
closed
Add possibility to clear signals or remove a single slot
0%
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.
Updated by Gerrit Code Review over 9 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
Updated by Gerrit Code Review about 9 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
Updated by Gerrit Code Review almost 9 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
Updated by Gerrit Code Review over 8 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
Updated by Timo Webler about 8 years ago
Can we close this issue? Duplicated issue? #65774
Updated by Gerrit Code Review almost 8 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
Updated by Benni Mack about 7 years 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.
Updated by Timo Webler over 6 years 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.
Updated by 
Updated by