Difference between revisions of "Template:Expensive"

From blackwiki
Jump to navigation Jump to search
imported>PrimeHunter
(fix link to mw:Help:Extension:ParserFunctions##ifexist, no ending colon since 2009)
imported>Davidwr
(+<small>''(further information)''</small>)
 
(3 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
| type = style
 
| type = style
 
| image = [[Image:Ambox warning yellow.svg|40x40px]]
 
| image = [[Image:Ambox warning yellow.svg|40x40px]]
| text = Due to a server limit of '''500''' "expensive parser function" calls <small>([[mw:Help:Extension:ParserFunctions##ifexist|#ifexist:]], [[mw:Help:Magic words#Technical metadata|PAGESIZE:]], and [[mw:Help:Magic words#Statistics|PAGESINCATEGORY:]])</small>, this template will only work properly for the first 500 calls.  When the limit is exceeded, the page is categorised [[:Category:Pages with too many expensive parser function calls]].
+
| text = Due to a server limit of '''500''' "expensive parser function" calls <small>([[mw:Help:Extension:ParserFunctions##ifexist|#ifexist:]], [[mw:Help:Magic words#Technical metadata|PAGESIZE:]], and [[mw:Help:Magic words#Statistics|PAGESINCATEGORY:]])</small>, this template or module will only work properly if the page using it has not already exceeded the limit.  When the limit is exceeded, the page using this template or module is categorised [[:Category:Pages with too many expensive parser function calls]]. <small>''([[Template:Expensive|further information]])''</small>
 
 
<small>View [//tools.wmflabs.org/catscan2/catscan2.php?wikilang=en&basecat=Pages_with_too_many_expensive_parser_function_calls&mode=ts&templates={{PAGENAMEE}}  Pages which have exceeded expensive parser call limit]</small>
 
 
}}<noinclude>
 
}}<noinclude>
  

Latest revision as of 18:01, 14 August 2020

Template documentation[view] [edit] [history] [purge]

Usage

  • {{Expensive}}

Place this at the top of documentation sub-pages of templates or modules which MAY call one or more "expensive parser functions." Include specific details, such as what parameters trigger expensive parser function usage, in the body of the template's documentation.

Special case
  • Templates unlikely to ever be the major reason a page reaches the 500-call limit
Use your best judgment about using this at the top of the template's documentation page, but DO document the expensive parser function usage somewhere in the template's documentation.

See also