Last modified: 2011-08-17 22:13:28 UTC
currently the <categorytree> tag disables parser cache. I was under the impression this was a big no-no from a performance standpoint (and that tag is used on high profile pages like the commons main page) The extension has a config variable - $wgCategoryTreeDisableCache. Setting it to false will stop the extension from disabling cache, which is probably a good thing - thus I suggest setting that setting to false. Anyways, if the fact <categorytree> calls $parser->disableCache() is a non-issue, please ignore this. See also bug 30428
Reedy fixed this: [15:46] <logmsgbot> !log reedy synchronized wmf-config/CommonSettings.php 'Setting to false' [15:46] <morebots> Logged the message, Master [15:47] <Reedy> !log That was Setting $wgCategoryTreeDisableCache to false. Stupid escaping Additionally you can now see the commons main page has <!-- Saved in parser cache with key commonswiki:pcache:idhash:1-0!*!0!default!!en!4!* and timestamp 20110817214446 --> (Guess I probably shouldn't have opened this bug given its essentially the same as the other one)
