Bug #98716
openCachingFrameworkGarbageCollectionTask does not fall back to default storage backend
0%
Description
According to the documentation, the default backend for the caching framework is the database.
https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/CachingFramework/FrontendsBackends/Index.html#database-backend
But the garbage collection task does not respect this and requires the backend config to be explicitly set, so the comparison to the selected backends works
'backend' => \TYPO3\CMS\Core\Cache\Backend\Typo3DatabaseBackend::class
The error already came up in #96438, but the solution is not to default this to null but to the database backend. The database in a 10.4 setup got a lot of cache entries since they only got cleaned up during a deployment and a cache flush call, but the scheduler just skipped it. The code for 11.5 was not touched besides the null default
#96504 is also related to this, but only tackled the field provider, not the actual execution of the cleanup
https://github.com/TYPO3/typo3/blob/c82d1929d6ee032edd33a42448a81e7c20998240/typo3/sysext/scheduler/Classes/Task/CachingFrameworkGarbageCollectionTask.php#L53
It would be great to have this stuff also fixed for 10.4, but i'd be fine if it only gets fixed in 11.5 and 12 since it can be adjusted by config.