Manual:$wgExpensiveParserFunctionLimit/pl
From Linux Web Expert
| <translate> Parser</translate>: $wgExpensiveParserFunctionLimit | |
|---|---|
| Maximum number of calls per parse to expensive parser functions such as PAGESINCATEGORY. |
|
| <translate> Introduced in version:</translate> | 1.13.0 (r32932) |
| <translate> Removed in version:</translate> | <translate> still in use</translate> |
| <translate> Allowed values:</translate> | (integer) |
| <translate> Default value:</translate> | 100 |
| <translate> Other settings:</translate> <translate> Alphabetical</translate> | <translate> By function</translate> | |
Szczegóły
Maximum number of calls per parse to expensive parser functions such as PAGESINCATEGORY. Expensive parser functions include:
- {{#ifexist:}} (z Extension:ParserFunctions)
- {{PAGESINCATEGORY}}/{{PAGESINCAT}} (a Magic Word)
- {{PAGESIZE}} (a Magic Word)
- {{REVISIONUSER}} and {{REVISIONTIMESTAMP}} when used with the optional argument to specify a different page
- {{CASCADINGSOURCES}} (a Magic Word)
- Some Lua MediaWiki-related functions (see Lua reference manual), including
mw.incrementExpensiveFunctionCount()which can be used to manually mark a Lua code path as expensive.
<syntaxhighlight>(since 1.39)- Search for
Parser::incrementExpensiveFunctionCount()calls to find more wikitext features that are considered expensive.
A limit report for the current page can be found as a comment in the HTML source of the page. Even without saving, the count for any wikitext can be checked by checking the html-source of the preview page for that wikitext.
