Commit b8826742 authored by Helmut Hummel's avatar Helmut Hummel
Browse files

[BUGFIX] Accessing unavailable site config triggers notice instead of warning

Accessing a not available configuration via TypoScript can be
intentional (e.g. by using it in an if check).
Therefore the log entry severity should rather be downgraded to a notice.

Releases: 10.4, 11.5, main
Resolves: #99465
Change-Id: I26ed4e96290ce6839c32cc60a7cbcf7fa24d0f2b
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/77289


Tested-by: Helmut Hummel's avatarHelmut Hummel <typo3@helhum.io>
Tested-by: core-ci's avatarcore-ci <typo3@b13.com>
Reviewed-by: Helmut Hummel's avatarHelmut Hummel <typo3@helhum.io>
parent 553c43b6
......@@ -4866,7 +4866,7 @@ class ContentObjectRenderer implements LoggerAwareInterface
try {
$retVal = ArrayUtility::getValueByPath($site->getConfiguration(), $key, '.');
} catch (MissingArrayPathException $exception) {
$this->logger->warning(sprintf('getData() with "%s" failed', $key), ['exception' => $exception]);
$this->logger->notice(sprintf('Configuration "%s" is not defined for site "%s"', $key, $site->getIdentifier()), ['exception' => $exception]);
}
}
break;
......
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