#110440Deprecation notice caused by 'PKG:' resource identifier in TYPO3_CONF_VARS.EXTENSIONS.backend.backendLogo
Description
- introduced the
PKG:<composer-name>:<path>resource identifier and advises integrators to adopt it:
The well-known EXT syntax can still be used for the time being. […] This syntax is not yet deprecated, but users are advised to switch to the new syntax for new projects.
Following that advice for $GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['backend']['backendLogo'] produces an E_USER_DEPRECATED notice on every backend request topbar rendering. The legacy EXT: form for the very same file produces none.
So the new, recommended form is penalised. The only way to silence it is to revert to the legacy syntax.
backendLogo is the only affected setting. Its siblings accept PKG: cleanly, which makes the behaviour look like an oversight rather than an intentional boundary.
| Setting | Consuming code | PKG: accepted |
|---|---|---|
loginLogo |
AuthenticationStyleInformation::getLogo() |
yes |
loginBackgroundImage |
AuthenticationStyleInformation::getBackgroundImageStyles() |
yes |
backendFavicon |
PageRendererBackendSetupTrait::getUriForFileName() |
yes |
backendLogo |
BackendController::assignTopbarDetailsToView() |
yes, but emits a deprecation |
The three working settings pass the identifier only to the SystemResource API (SystemResourceFactory::createPublicResource() plus SystemResourcePublisherInterface::generateUri()). backendLogo additionally resolves it to an absolute file system path.
Expected behaviour
A PKG: identifier in backendLogo behaves like a PKG: identifier in its siblings: without a deprecation notice.
Analysis
Classes/Controller/BackendController.php evaluates the setting twice:
The new API for the URL, an absolute path, needed for the file_exists() guard and where ImageInfo determines width and height (and the @2x high resolution case). GeneralUtility::getFileAbsFileName() delegates to ExtensionManagementUtility::resolvePackagePath(), which emits the deprecation for PKG: identifiers.
Secondary issue: the stated removal milestone has passed
The notice says the behaviour “will be removed in TYPO3 v14 LTS” but the trigger_error() is still present in 14.3.6, so the named milestone has shipped without the removal happening. The message should name a milestone that is still ahead.