Actions
Bug #97665
closedExtensionManagmentUtility-Exception: Call to a member function isPackageActive() on null
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2022-05-21
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
11
PHP Version:
7.4
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
I have a conflict between my Extension Timer and Whysiwyg, which use the added service.yaml and the extension luxletter.
See Screenshot.
I used the patch to prevent this problem.
I added my composer.json.
Files
Updated by Dieter Porth over 2 years ago
- File local_history_ExtensionManagementUtility_II.patch local_history_ExtensionManagementUtility_II.patch added
Correct Patch with overall changes
Updated by Chris Müller over 2 years ago
Luxletter uses a wrong condition in Services.php.
ExtensionManagementUtility::isLoaded() works accidently in TYPO3 v10 but not in v11 anymore. The correct usage would be $containerBuilder->hasDefinition() (which also works in v10). So, this seems to be in issue in Luxletter.
Updated by Chris Müller over 2 years ago
Background: see https://review.typo3.org/c/Packages/TYPO3.CMS/+/71272
Updated by Georg Ringer over 2 years ago
opened an issue at https://github.com/in2code-de/luxletter/issues/120
Updated by Georg Ringer over 2 years ago
- Status changed from New to Closed
luxletter release is on its way
Actions