Deprecation: #94117 - Register extbase type converters as services

See Issue #94117


Because extbase type converters are no longer registered via \TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerTypeConverter() but as container services, also the configuration, such as sourceType or targetType is now defined in the Services.yaml.

Therefore, the following configuration related properties and methods of \TYPO3\CMS\Extbase\Property\TypeConverter\AbstractTypeConverter have been deprecated:

  • \TYPO3\CMS\Extbase\Property\TypeConverter\AbstractTypeConverter::$sourceTypes
  • \TYPO3\CMS\Extbase\Property\TypeConverter\AbstractTypeConverter::$targetType
  • \TYPO3\CMS\Extbase\Property\TypeConverter\AbstractTypeConverter::$priority
  • \TYPO3\CMS\Extbase\Property\TypeConverter\AbstractTypeConverter::getSupportedSourceTypes()
  • \TYPO3\CMS\Extbase\Property\TypeConverter\AbstractTypeConverter::getSupportedTargetType()
  • \TYPO3\CMS\Extbase\Property\TypeConverter\AbstractTypeConverter::getPriority()
  • \TYPO3\CMS\Extbase\Property\TypeConverter\AbstractTypeConverter::canConvertFrom()

The methods have also been removed from the TypeConverterInterface, see changelog.


Since those properties and methods were important for registering and configuring type converters but are replaced with type converter registrations in Services.yaml, they are now obsolete and without functionality.

If defined in an own type converter, those properties and methods can be removed there as well.

Affected Installations

All installations with custom type converters, extending AbstractTypeConverter and relying on those properties and methods.


In custom type converters, drop mentioned properties and methods and don’t access said properties and methods of AbstractTypeConverter from outside.