Project

General

Profile

Actions

Bug #64079

closed

Extension manager doesn't emit "hasInstalledExtensions" signal after extension upload

Added by Aimeos no-lastname-given over 9 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extension Manager
Start date:
2015-01-02
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.5
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

Description

Hi Susanne

Found a problem in the extension manager code which doesn't emit the "hasInstalledExtensions" signal if a .zip or .tx file is uploaded in the extension manager within the TYPO3 backend. If an extension is downloaded from TER, the DownloadController including the ExtensionManagementService class is used which emits the signal after installing the extension. Uploading an extension is handled by the UploadExtensionFileController class that calls the InstallUtility directly without emitting the signal.

The best option would be to use the ExtensionManagementService in the UploadExtensionFileController class as well. I've tested this with TYPO3 6.2 and 7.0 and it would be nice if this could be fixed in 6.2 LTS as well.

Thanks


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #58016: module list is not refreshed after installing new extensionsClosed2014-04-17

Actions
Actions #1

Updated by Wouter Wolters over 9 years ago

  • Assignee deleted (Susanne Moog)

Please do not assign directly to a person. Thanks!

Actions #2

Updated by Wouter Wolters over 9 years ago

  • Target version set to 7.3 (Packages)
Actions #3

Updated by Nicole Cordes about 9 years ago

  • Status changed from New to Needs Feedback

This can't be solved easily and IMHO separate between local and TER version is much better, than a single one. You could additionally register your slot to the signal

TYPO3\CMS\Extensionmanager\Utility\InstallUtility::afterExtensionInstall

Actions #4

Updated by Aimeos no-lastname-given about 9 years ago

Hi Nicole

This can't be solved easily and IMHO separate between local and TER version is much better, than a single one. You could additionally register your slot to the signal

TYPO3\CMS\Extensionmanager\Utility\InstallUtility::afterExtensionInstall

Tried it with the code below in ext_localconf.php but it didn't executed Aimeos\Aimeos\Setup->executeOnSignal():

$signalSlotDispatcher->connect(
    'TYPO3\\CMS\\Extensionmanager\\Utility\\InstallUtility',
    'afterExtensionInstall',
    'Aimeos\\Aimeos\\Setup',
    'executeOnSignal'
);

This works at least for not manually uploaded extensions:

$signalSlotDispatcher->connect(
    'TYPO3\\CMS\\Extensionmanager\\Service\\ExtensionManagementService',
    'hasInstalledExtensions',
    'Aimeos\\Aimeos\\Setup',
    'executeOnSignal'
);
Actions #5

Updated by Benni Mack almost 9 years ago

  • Target version changed from 7.3 (Packages) to 7.4 (Backend)
Actions #6

Updated by Alexander Opitz almost 9 years ago

  • Status changed from Needs Feedback to New
Actions #7

Updated by Susanne Moog over 8 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #8

Updated by Benni Mack over 8 years ago

  • Target version changed from 7.5 to 7 LTS
Actions #9

Updated by Riccardo De Contardi over 8 years ago

  • Target version changed from 7 LTS to Candidate for Major Version
Actions #10

Updated by Susanne Moog about 4 years ago

  • Status changed from New to Closed

The code now uses the managementService in both cases. Additionally, since the introduction of events `AfterPackageActivationEvent` can be used for both.

Actions

Also available in: Atom PDF