User talk:Euss/todo: Difference between revisions

From PS4 Developer wiki
Jump to navigation Jump to search
Line 57: Line 57:


== $wgExpensiveParserFunctionLimit ==
== $wgExpensiveParserFunctionLimit ==
If this wiki is ever going to use language templates, make sure the parsing does not exceed the limit (either reduce the amount of languages thus the parsing, or increase the limit) If the limit is exceeded, not all items will be parsed and thus the links for consecutive languages will not be made. The parsing count can be seen inside the source of the page as seen in this example:
If this wiki is ever going to use language templates, make sure the parsing does not exceed the limit (either reduce the amount of languages thus the parsing, or increase the limit) If the limit is exceeded (
Pages that exceed this limit are automatically categorized into [[:Category:Pages with too many expensive parser function calls]]), not all items will be parsed and thus the links for consecutive languages will not be made. The parsing count can be seen inside the source of the page as seen in this example:
<source lang="html4strict">
<source lang="html4strict">
<!--  
<!--  
Line 70: Line 71:
</source>
</source>
In above example, the language template was reduced by removing languages that are not covered by PS4 releases to begin with, while the page in question has over 100 language subpages
In above example, the language template was reduced by removing languages that are not covered by PS4 releases to begin with, while the page in question has over 100 language subpages
<source lang="html4strict">
<!--
NewPP limit report
Preprocessor visited node count: 1598/1000000
Preprocessor generated node count: 4221/1000000
Post‐expand include size: 24926/2097152 bytes
Template argument size: 3880/2097152 bytes
Highest expansion depth: 9/40
Expensive parser function count: 61/100
-->
</source>
In [[User_talk:Euss/stats|above example]], the amount of used expensive parser function calls was reduced to only do stats for the most important categories


See also: http://www.mediawiki.org/wiki/Manual:$wgExpensiveParserFunctionLimit
See also: http://www.mediawiki.org/wiki/Manual:$wgExpensiveParserFunctionLimit

Revision as of 18:47, 29 January 2014

ToDo

Check missing/needed extensions


Note: If someone else does any of the above, please use <strike> old text </strike> to mark it on the list so that it can be crosschecked


Test 123

Imagemaps

$wgExpensiveParserFunctionLimit

If this wiki is ever going to use language templates, make sure the parsing does not exceed the limit (either reduce the amount of languages thus the parsing, or increase the limit) If the limit is exceeded ( Pages that exceed this limit are automatically categorized into Category:Pages with too many expensive parser function calls), not all items will be parsed and thus the links for consecutive languages will not be made. The parsing count can be seen inside the source of the page as seen in this example:

<!-- 
NewPP limit report
Preprocessor visited node count: 1589/1000000
Preprocessor generated node count: 3629/1000000
Post‐expand include size: 27853/2097152 bytes
Template argument size: 4210/2097152 bytes
Highest expansion depth: 10/40
Expensive parser function count: 45/100
-->

In above example, the language template was reduced by removing languages that are not covered by PS4 releases to begin with, while the page in question has over 100 language subpages

<!-- 
NewPP limit report
Preprocessor visited node count: 1598/1000000
Preprocessor generated node count: 4221/1000000
Post‐expand include size: 24926/2097152 bytes
Template argument size: 3880/2097152 bytes
Highest expansion depth: 9/40
Expensive parser function count: 61/100
-->

In above example, the amount of used expensive parser function calls was reduced to only do stats for the most important categories

See also: http://www.mediawiki.org/wiki/Manual:$wgExpensiveParserFunctionLimit