Project

General

Profile

Actions

Feature #62271

closed

Install Tool unavailable if there are unresolved dependencies

Added by Christoph Dörfel over 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2014-10-16
Due date:
% Done:

0%

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

Description

If a TYPO3 extension / package is not listed in PackageStates and another extension / package depends on it, the DependencyResolver throws and UnexpectedValueException.

This exception is uncaught even in the install tool, where we should be able to resolve such problems - either by deactivating the extension with the missing dependency or by updating the PackageStates file.

This is an extreme edge case and it won't happen very often. For the sake of usability this exception should be caught and handled accordingly in the install tool.

PHP Fatal error:  Uncaught exception 'UnexpectedValueException' with message 'The package "myextension" depends on "nothere" which is not present in the system.' in /typo3/sysext/core/Classes/Package/DependencyResolver.php:140
Stack trace:
#0 /typo3/sysext/core/Classes/Package/DependencyResolver.php(240): TYPO3\CMS\Core\Package\DependencyResolver->buildDependencyGraphForPackages(Array, Array)
#1 /typo3/sysext/core/Classes/Package/DependencyResolver.php(51): TYPO3\CMS\Core\Package\DependencyResolver->buildDependencyGraph(Array)
#2 /typo3/sysext/core/Classes/Package/PackageManager.php(701): TYPO3\CMS\Core\Package\DependencyResolver->sortPackageStatesConfigurationByDependency(Array)
#3 /typo3/sysext/core/Resources/PHP/TYPO3. in /typo3/sysext/core/Classes/Package/

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #57120: Upgrade from 6.1.7 to 6.2beta7 / Install Tool fails / 'The package "X" depends on "Y" which is not present in the system'Closed2014-03-20

Actions
Actions #1

Updated by Mathias Schreiber about 9 years ago

  • Status changed from New to Closed

Taken into account in #63909.
The issues are not linked on purpose, so the refactoring ticket does not get bloated with relations.

Actions

Also available in: Atom PDF