Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • typo3 typo3
  • Project information
    • Project information
    • Activity
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Insights
    • Repository
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • typo3typo3
  • typo3typo3
  • Repository
Switch branch/tag
  • typo3
  • typo3
  • sysext
  • frontend
  • Classes
  • ContentObject
  • ContentObjectRenderer.php
Find file BlameHistoryPermalink
  • Helmut Hummel's avatar
    [BUGFIX] Accessing unavailable site config triggers notice instead of warning · b8826742
    Helmut Hummel authored Jan 05, 2023
    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>
    b8826742