Deprecation: #94619 - Extbase ObjectManager¶
See Issue #94619
The Extbase ObjectManager as the legacy core object lifecycle and dependency injection solution has been marked discouraged with TYPO3 v10 and its introduction of the Symfony based dependency injection solution already.
TYPO3 v11 no longer uses the Extbase ObjectManager - only in a couple of places as fallback for third party extensions. The entire construct has now been marked as deprecated and will be removed with v12:
TYPO3\CMS\Extbase\Object\ObjectManagerInterface- Main interface
TYPO3\CMS\Extbase\Object\ObjectManager- Main implementation
TYPO3\CMS\Extbase\Object\Container\Container- Internal lifecycle management
TYPO3\CMS\Extbase\Object\Exception- Base exception
TYPO3\CMS\Extbase\Object\Exception\CannotBuildObjectException- Detail exception
TYPO3\CMS\Extbase\Object\Container\Exception\CannotReconstituteObjectException- Detail exception
TYPO3\CMS\Extbase\Object\Container\Exception\UnknownObjectException- Detail exception
TYPO3\CMS\Extbase\SignalSlot\Exception\InvalidSlotException- Detail exception, obsolete by deprecation of Extbase signal slot dispatcher already.
TYPO3\CMS\Extbase\SignalSlot\Exception\InvalidSlotReturnException- Detail exception, obsolete by deprecation of Extbase signal slot dispatcher already.
Directly or indirectly calling
will trigger a PHP
Extensions that have been properly cleaned up for TYPO3 v10 compatibility are not affected.
Extensions still relying on Extbase ObjectManager are strongly encouraged to
Symfony based DI instead.
The extension scanner will find usages of the above classes and interfaces and shows them as deprecated with a strong match.