[Mediawiki-l] Server Side Caching for Default Installation

Jon Belanger jon at chem.umass.edu
Thu Mar 16 19:46:56 UTC 2006

Hash: SHA1

On Mar 16, 2006, at 1:55 PM, Brion Vibber wrote:

>> It would be nice for MediaWiki to truncate the table for you if you
>> change $wgCachePages from it's default to FALSE.  Or anyway, just have
>> $wgCachePages be false by default.
> As of MediaWiki 1.6 $wgCacheEpoch is updated along with the timestamp 
> of your
> LocalSettings.php on new installations. You can add this yourself if 
> you expect
> to constantly make such changes:
> # When you make changes to this configuration file, this will make
> # sure that cached pages are cleared.
> $configdate = gmdate( 'YmdHis', @filemtime( __FILE__ ) );
> $wgCacheEpoch = max( $wgCacheEpoch, $configdate );
>> Some of my questions still stand, why do the preferences in the user
>> table effect wether or not to use the cache, I wonder??
> Generally they don't; they effect which cached copy you get.

>> #1 Why is caching on when I've set $wgCachePages = false
> That's only for client-side caching. The parser cache is separate.
>> #2 Why the odd behavior with the "extra" preferences.  Why does it 
>> work
>> without then, and why does it break with then.   More to the point, 
>> why
>> does this effect server side caching?
> Parser cache is keyed on various user options which affect rendering.

So, you've said that my problem here is the Parser cache.  Does 
wgCacheEpoch effect the Parser cache?




More information about the MediaWiki-l mailing list