Project

General

Profile

Actions

Task #100067

closed

Streamline logging in TypoScriptFrontendController->set_no_cache

Added by Thomas Hohn over 1 year ago. Updated 10 months ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Logging
Start date:
2023-03-03
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
11
PHP Version:
8.1
Tags:
Complexity:
Sprint Focus:

Description

TYPO3 will, when set_no_cache is called, issue a log WARNING that contains either a caller provided reason for why it was called or alternatively a pointer to what code called it, generated by calling the backtrace function.
In addition to the plain set_no_cache logging case, there is also the related but somewhat separate "disableNoCacheParameter" handling that logs as a WARNING if set_no_cache is logged, but is ignored by the [TYPO3_CONF_VARS][FE][disableNoCacheParameter]. This also triggers a WARNING.

Instead both scenarios should just issue a Notice.
We could deprecate the $internal variable in v12 as proposed in https://forge.typo3.org/issues/97815


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #97815: Excessive logging in TypoScriptFrontendController set_no_cacheClosed2022-06-27

Actions
Actions

Also available in: Atom PDF