Commit 6e25062a authored by Christian Kuhn's avatar Christian Kuhn
Browse files

[BUGFIX] Avoid empty entries in scheduler CF garbage collection

When having an extension loaded that specifies a cache
without a specific backend like ext:adminpanel, the caching
framework falls back to default Typo3DatabaseBackend.

The scheduler task "Caching framework garbage collection"
does not reflect this and renders an empty entry when no
specific backend is configured.

Fix this by adding the fallback to the tasks additional
field provider, too.

Resolves: #96504
Releases: main, 11.5
Change-Id: I985ff3b9888723986e7938238be99e45c1999064

Tested-by: core-ci's avatarcore-ci <>
Tested-by: Andreas Fernandez's avatarAndreas Fernandez <>
Tested-by: Helmut Hummel's avatarHelmut Hummel <>
Tested-by: Christian Kuhn's avatarChristian Kuhn <>
Reviewed-by: Andreas Fernandez's avatarAndreas Fernandez <>
Reviewed-by: Helmut Hummel's avatarHelmut Hummel <>
Reviewed-by: Christian Kuhn's avatarChristian Kuhn <>
parent 9ce15af3
......@@ -135,7 +135,7 @@ class CachingFrameworkGarbageCollectionAdditionalFieldProvider extends AbstractA
$cacheConfigurations = $GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations'];
if (is_array($cacheConfigurations)) {
foreach ($cacheConfigurations as $cacheConfiguration) {
$backend = (string)($cacheConfiguration['backend'] ?? '');
$backend = (string)($cacheConfiguration['backend'] ?? Typo3DatabaseBackend::class);
if (!in_array($backend, $backends, true)) {
$backends[] = $backend;
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment