Feature #20849

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

Added by Michael Stucki over 7 years ago. Updated over 6 years ago.

Status:Closed Start date:2009-08-07
Priority:Should have Due date:
Assigned To:Michael Stucki % Done:


Target version:-
PHP Version:4.3 Complexity:
Tags: Sprint Focus:


$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 Magnifier (2.2 kB) Administrator Admin, 2009-08-07 15:56

bug_11669_no_cache_reason_w.diff Magnifier (1.1 kB) Administrator Admin, 2009-08-07 15:56

0011669_v2.patch Magnifier (1.5 kB) Administrator Admin, 2009-09-16 13:11

0011669_v3.patch Magnifier (1.7 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
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

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


#1 Updated by Oliver Hader over 7 years ago

Committed to SVN Trunk (rev. 5956)

Also available in: Atom PDF