$smwgQueryResultCacheRefreshOnPurge

Configuration parameter details:
Name	$smwgQueryResultCacheRefreshOnPurge
Description	Sets whether it is possible to manually refresh the query cache by doing a "purge" action
Default setting	true
(Other) available settings	false Allows to disable the purging of the results cache
Software	Semantic MediaWiki
Since version	2.5.0
Until version	still available
Configuration	Cache
Keyword	caching · object cache · performance · query performance · query result cache · experimental

$smwgQueryResultCacheRefreshOnPurge is a configuration parameter that sets whether it is possible to manually refresh the query cache by doing a "purge" action (&action=purge). It was introduced in Semantic MediaWiki 2.5.0.1

This configuration parameter only takes effect if the query results cache was enabled.

Default setting

$smwgQueryResultCacheRefreshOnPurge = true;

This means that by default purging the query cache is allowed.

Changing the default setting

To modify the setting to this configuration parameter, add one of the following lines to your "LocalSettings.php" file after the enableSemantics() call:

Disable manual purging of the cache

$smwgQueryResultCacheRefreshOnPurge = false;

This means that purging the query cache is not allowed. The wiki will then retain the cache of embedded queries and their results fetched from the query engine.

See also

Query result caching

• Help page on the query result cache
• Help page on configuration parameter $smwgQueryResultCacheTypeSets whether the query result cache may be used
• Help page on configuration parameter $smwgQueryResultCacheLifetimeSets the cache lifetime of embedded queries and their results fetched from the query engine
• Help page on configuration parameter $smwgQueryResultNonEmbeddedCacheLifetimeSets the cache lifetime of non-embedded queries and their results fetched from the query engine

Embedded query updates

• Help page on embedded query updates
• Help page on configuration parameter $smwgEnabledQueryDependencyLinksStoreSets whether tracking and storing of dependencies of embedded queries may be used