Bug #53178
Package loading order does not respect Extension dependencies
| Status: | Closed | Start date: | 2013-10-28 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 100% |
|
| Category: | - | Spent time: | - | |
| Target version: | 6.2.0 | |||
| TYPO3 Version: | 6.2 | Is Regression: | No | |
| PHP Version: | 5.4 | Sprint Focus: | ||
| Complexity: |
Description
It seems that the dependency checks currently only core packages.
The reason for this seems to be the naming of the requirements in the ext_emconf.php files. Since there only the extension names are required they are not considered as valid package keys in \TYPO3\Flow\Package\Package->getPackageMetaData().
If this check is disabled the dependencies will be considered but when an Extension has a dependency for a system extension \TYPO3\CMS\Core\Package\PackageManager->buildDependencyGraphForPackages() will throw an Exceptions because it only knows about non-system Extensions and it will also fail on requirements for php or typo3.
Extension loading order is important because Extensions might manipulate the configuration of other Extensions and therefore need to be loaded after them.
1.diff
(697 Bytes)
Related issues
History
#1 Updated by Dmitry Dulepov over 1 year ago
- File 1.diff added
Temporarily fixed this in my installation with the attached patch. This is NOT a real solution, it is just to let the user go&test TYPO3 further.
#2 Updated by Thomas Maroschik over 1 year ago
- Status changed from New to Closed
- % Done changed from 0 to 100
I think we fixed this already with Markus Kleins dependency patches.