Bug #87503
closed
Epic #83968: PSR-11 Initiative
ErrorPageController relies on an available PackageManager
100%
Description
When the ProductionExceptionHandler is used and an exception occures before the PackageManager has been initialized, the method ExtensionManagementUtility::extPath() can not be used, as it relies on the PackageManager to retrieve a packages path.
As ErrorPageController needs to be able to handle exception during early bootstrap it should bypass ExtensionManagementUtility/PackageManager to be always able to retrieve paths for required core extensions like core and backend.
Updated by Benjamin Franzke almost 6 years ago
- Related to Bug #87175: activating SEO or Redirects core extension breaks the system added
Updated by Gerrit Code Review almost 6 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59507
Updated by Gerrit Code Review almost 6 years ago
Patch set 1 for branch 9.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/59518
Updated by Benjamin Franzke almost 6 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 90305f1b1de2c70e4fe958ae231866488816e42f.
Updated by Ronald Wopereis almost 6 years ago
I get the error when a syntax error occurs in typo3conf/PackageStates.php
After adding couple of lines i could see that packageManager is EMPTY for key 'core'
Debug:
/usr/share/typo3/typo3_src-9.5.3/typo3/sysext/core/Classes/Utility/ExtensionManagementUtility.php
added three lines at beginning of public static function extPath($key, $script = '')
if (empty(static::$packageManager)) {
throw new \BadFunctionCallException('TYPO3 Fatal Error: packageManager is EMPTY for key '.$key, 1234567890);
}
Updated by