Feature #20849

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

Added by Michael Stucki almost 8 years ago. Updated almost 7 years ago.

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

0%

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)

bug_11669_no_cache_reason.diff View (2.19 KB) Administrator Admin, 2009-08-07 15:56

bug_11669_no_cache_reason_w.diff View (1.14 KB) Administrator Admin, 2009-08-07 15:56

0011669_v2.patch View (1.47 KB) Administrator Admin, 2009-09-16 13:11

0011669_v3.patch View (1.75 KB) Administrator Admin, 2009-09-17 20:42


Related issues

Related to Core - Task #43506: Provide a reason if set_no_cache() is called Resolved 2012-12-01

Associated revisions

Revision 6062769a (diff)
Added by Philipp Gampe over 4 years ago

[TASK] Provide a reason if set_no_cache() is called

Since #20849, we can specify a reason why we call
GLOBALS['TSFE']->set_no_cache().

Provide a reason for all calls done in core.

Resolves: #43506
Related: #20849
Releases: 6.1

Change-Id: Id786a041ef5d9f1db49d644459a593aaf54b5018
Reviewed-on: http://review.typo3.org/16925
Reviewed-by: Stefan Neufeind
Reviewed-by: Dmitry Dulepov
Tested-by: Dmitry Dulepov

History

#1 Updated by Oliver Hader almost 8 years ago

Committed to SVN Trunk (rev. 5956)

Also available in: Atom PDF