Project

General

Profile

Actions

Bug #78868

closed

Check for broken extensions should check ext_emconf.php

Added by Franz Holzinger over 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2016-12-03
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
5.6
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

The Extension Manager throws exceptions after the upgrade from TYPO3 6.2.27 to 7.6.14. The Install Tool should have reported those problems before.
Those problematic extensons have never been installed. They are old and inside the typo3conf/ext folder. However they crash the EM:

Uncaught TYPO3 Exception
#1439552059: The extension "dd_extensionframework" has invalid version constraints in conflicts section. Extension key is missing! (More information)

TYPO3\CMS\Core\Package\Exception\InvalidPackageManifestException thrown in file
/var/www/html/typo3_src-7.6.14/typo3/sysext/core/Classes/Package/PackageManager.php in line 1022.

22 TYPO3\CMS\Core\Package\PackageManager::mapExtensionManagerConfigurationToComposerManifest("dd_extensionframework", array, stdClass)

/var/www/html/typo3_src-7.6.14/typo3/sysext/core/Classes/Package/PackageManager.php:

00955:             $extensionManagerConfiguration,
00956:             $composerManifest ?: new \stdClass()

00957:         );

00958: 
00959:         return $composerManifest;

21 TYPO3\CMS\Core\Package\PackageManager::getComposerManifest("/var/www/html/typo3conf/ext/dd_extensionframework/")

/var/www/html/typo3_src-7.6.14/typo3/sysext/core/Classes/Package/PackageManager.php:

00347:             }
00348:             try {

00349:                 $composerManifest = $this->getComposerManifest($packagePath);

00350:                 $packageKey = $this->getPackageKeyFromManifest($composerManifest, $packagePath, $packagesBasePath);
00351:                 $this->composerNameToPackageKeyMap[strtolower($composerManifest->name)] = $packageKey;

20 TYPO3\CMS\Core\Package\PackageManager::scanAvailablePackages("PackageManagement::packagesMayHaveChanged")

19 call_user_func_array(array, array)

/var/www/html/typo3_src-7.6.14/typo3/sysext/extbase/Classes/SignalSlot/Dispatcher.php:

00138:             }
00139: 

00140:             $slotReturn = call_user_func_array([$object, $slotInformation['method']], $preparedSlotArguments);

00141: 
00142:             if ($slotReturn) {

18 TYPO3\CMS\Extbase\SignalSlot\Dispatcher::dispatch("PackageManagement", "packagesMayHaveChanged")

/var/www/html/typo3_src-7.6.14/typo3/sysext/extensionmanager/Classes/Utility/ListUtility.php:

00150:     protected function emitPackagesMayHaveChangedSignal()
00151:     {

00152:         $this->signalSlotDispatcher->dispatch('PackageManagement', 'packagesMayHaveChanged');

00153:     }
00154: 

That extension uses invalid constraints:
(see attached file)

    'constraints' => array(
        'depends' => array(
            'typo3' => '',
            'php' => '',
            'cms' => '',
        ),
        'conflicts' => array(
            '' => '',
        ),
    ),
    'suggests' => array(
    ),

Files

ext_emconf.php (1.97 KB) ext_emconf.php Franz Holzinger, 2016-12-03 09:31
ext_emconf.php (1.07 KB) ext_emconf.php Franz Holzinger, 2016-12-03 09:35

Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Feature #73015: Add ext_emconf.php validatorClosedGeorg Ringer2016-01-29

Actions
Actions

Also available in: Atom PDF