Project

General

Profile

Actions
Copy link

Feature #20849

closed

Provide a reason for why tslib_fe::set_no_cache() has been triggered

Added by Michael Stucki over 15 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Michael Stucki
Category:
-
Target version:
-
Start date:
2009-08-07
Due date:
% Done:

0%

Estimated time:
PHP Version:
4.3
Tags:
Complexity:
Sprint Focus:

Description

$TSFE->set_no_cache() uses t3lib_div::sysLog() to log why the caching had been disabled.

Currently this is always done by identifying the trigger using a backtrace. This is not always helpful, in fact a more precise message would be much more helpful.

The new $reason parameter stays optional, so if it's not supplied, the old behaviour remains (identify and output the trigger).
(issue imported from #M11669)

Files

Download all files
bug_11669_no_cache_reason.diff (2.19 KB) bug_11669_no_cache_reason.diff Administrator Admin, 2009-08-07 15:56
bug_11669_no_cache_reason_w.diff (1.14 KB) bug_11669_no_cache_reason_w.diff Administrator Admin, 2009-08-07 15:56
0011669_v2.patch (1.47 KB) 0011669_v2.patch Administrator Admin, 2009-09-16 13:11
0011669_v3.patch (1.75 KB) 0011669_v3.patch Administrator Admin, 2009-09-17 20:42

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Task #43506: Provide a reason if set_no_cache() is calledClosed2012-12-01

Actions
Actions
Copy link

Also available in: Atom PDF