Manual:$wgExpensiveParserFunctionLimit
| Parser: $wgExpensiveParserFunctionLimit | |
|---|---|
| Maximum number of calls per parse to expensive parser functions such as PAGESINCATEGORY. |
|
| Introducido en la versión: | 1.13.0 (r32932) |
| Eliminado en la versión: | aún se usa |
| Valores permitidos: | (entero) |
| Valor predeterminado: | 100 |
| Otras configuraciones: Alfabéticamente | Por Función | |
Detalles
Maximum number of calls per parse to expensive parser functions such as PAGESINCATEGORY. Expensive parser functions include:
- {{#ifexist:}} (from Extensión:ParserFunctions)
- {{PAGESINCATEGORY}}/{{PAGESINCAT}} (una Palabra mágica)
- {{PAGESIZE}} (una Palabra mágica)
- {{REVISIONUSER}} and {{REVISIONTIMESTAMP}} when used with the optional argument to specify a different page
- {{CASCADINGSOURCES}} (una Palabra mágica)
- 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>(introducido en 1.39 phab:T316858)- 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.