#110110Cache warmup triggers deprecations for deprecated Core XLIFF files
Description
Summary
In TYPO3 14.3.4, running the system cache warmup triggers deprecation notices for Core XLIFF files that are already marked as deprecated or moved by Core itself.
This happens although no project or extension code explicitly references those deprecated language files.
Version scope
This was reproduced with TYPO3 14.3.4.
The current main branch is aliased as 15.0.x-dev and does not appear to be affected in the same way, because MOVED_FILES and DEPRECATED_FILES in TYPO3\CMS\Core\Localization\LocalizationFactory are currently empty there.
Steps to reproduce
Run the system cache warmup on a TYPO3 14.3.4 installation with deprecation logging enabled:
vendor/bin/typo3 cache:flush --group system vendor/bin/typo3 cache:warmup --group system
Actual result
Deprecation notices are logged for Core-owned language files, for example:
TYPO3 Deprecation Notice: The file "EXT:core/Resources/Private/Language/locallang_mod_admintools.xlf" is deprecated. Please use a label from a different language file instead. TYPO3 Deprecation Notice: The file "EXT:backend/Resources/Private/Language/locallang_mod.xlf" is deprecated. Please use a label from a different language file instead. TYPO3 Deprecation Notice: The file "EXT:install/Resources/Private/Language/BackendModule.xlf" is deprecated. Please use a label from a different language file instead.
In the affected installation, the deprecation log contained 400 entries: 25 unique Core XLIFF files, each logged multiple times during warmup.
Expected result
System cache warmup should not trigger deprecation notices for deprecated or moved Core language files.
Deprecation notices should still be emitted when project or extension code explicitly uses an old language file reference.
Technical background
TYPO3\CMS\Core\Localization\CacheWarmer collects default label files from all active packages during system cache warmup:
TYPO3\CMS\Core\Localization\LocalizationFactory already contains lists of moved and deprecated language files in TYPO3 14.3.4:
LocalizationFactory.php, moved and deprecated files, v14.3.4
The deprecation is triggered when such a file is processed:
LocalizationFactory.php, deprecation trigger, v14.3.4
As a result, Core-internal eager loading during cache warmup can produce deprecation notices that do not point to actionable project or extension code.
Why this matters
Deprecation logs should help identify code that still uses deprecated APIs or file references.
In this case, the log entries are caused by Core-internal cache warmup. This creates noise during deployments and manual warmup runs, while there is no concrete consumer code to migrate.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.