Bug #58875
closed
EM crashes with exception resolving depencies
0%
Description
When you try to active an extension which depends on another extension which in turn is activated by $GLOBALS['TYPO3_CONF_VARS']['EXT']['runtimeActivatedPackages'] then an uncaught exception is raised:
The package "foo" depends on "bar" which is not present in the system.
It seems that the EM checks at first (correctly) for all active extensions, but the package manager later on looks only at 'PackageStates.php'. Of course (?) the extensions installed by 'runtimeActivatedPackages' is not set to 'active' in 'PackageStates.php' which leads to this discrepancy. This must at least be handled gracefully.
Updated by
Updated by Philipp Gampe almost 10 years ago
IMHO this should only be valid for runtime activated packages themselves. Meaning, if a package that is activated on runtime has a dependency to another runtime activated, active package, then this should not throw a warning.
If a regular package is activated and the dependency is only fulfilled by a runtime activated package, then the error is totally valid. We cannot assume that a runtime activated package is always active.
Updated by Mathias Schreiber over 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.
Since composer will ALWAYS resolve ALL dependencies such a stale state could only be achieved by fiddling manually where you're not supposed to fiddle