Template:$wgParserCacheUseJson/en: Difference between revisions
From Bonkipedia
[[mw:]]>FuzzyBot (Updating to match new version of source page) |
ManfredoDo (talk | contribs) m (1 revision imported: Workaround and Utility Templates) |
(No difference)
| |
Latest revision as of 17:53, 12 November 2022
 | <translate> This feature was removed completely in version <tvar name=ver>1.39.0</tvar>.</translate> |
| <translate> Content handlers and storage</translate>: $wgParserCacheUseJson | |
|---|---|
| Enable JSON serialization for ParserCache. |
|
| <translate> Introduced in version:</translate> | 1.36.0 (Gerrit change 633513; git #0c059b73) |
| <translate> Deprecated in version:</translate> | 1.36.0 (Gerrit change 644316; git #d45b16ee) |
| <translate> Removed in version:</translate> | 1.39.0 (Gerrit change 790397; git #697f28df) |
| <translate> Allowed values:</translate> | <translate> Unspecified</translate> |
| <translate> Default value:</translate> | true |
| <translate> Other settings:</translate> <translate> Alphabetical</translate> | <translate> By function</translate> | |
Details
Enable JSON serialization for ParserCache.
In 1.36 the default serialization format for ParserCache has been changed from PHP serialization to JSON serialization. The cache is still compatible with old PHP-serialized entries, so for the most part the change should be unnoticed. However in case some extensions are installed which write non-JSON-serializable data to ParserOutput::setExtensionData, the cache will break for some pages. Setting this to false makes ParserCache use PHP serialization format for writing new cache entries, and all the cache entries already written in JSON are discarded.
