Errors on certain LotS item pages

Jump to: navigation, search
Edited by author.
Last edit: 18:10, 29 July 2013

Hey Zoy, I've been noticing errors on the LotS Item list pages. If you follow a link to one of the affected items, the links generate normally. For example, navigate to LotS/items/Officers, then search for Smeeg Valpug. If you look at the "Obtained" column on the far left, you should see "Please enter a valid raid name" displaying instead of a clickable link to the raid. If you open Smeeg Valpug's page, the raid links display properly.

I wrote the template to show the "please enter a valid raid name" text only when the user inputs a raid that does not exist.

I'm not sure what is causing this. It might also be an issue that only affects my computer, or affects other computers differently, but I have access to other computers to test this idea.

Klaxxin (talk)14:46, 9 November 2012

This issue is caused because there are a TON of parser functions on the page... This is occurring because we have a ton of things such as RaidLinks which use {{#ifexist}} 2 times. Every template with a {{# }} call in it costs a certain amount of processing time, and there is a max amount the wiki will do before stopping.

That is why the page gets Category: Pages with too many expensive parser function calls put at the bottom.

There are a few solutions here, we can remove some of the {{#s out of templates, which I looked into doing this to RaidLink but it appears both of them are needed based on how you are using it. Maybe we can find a few templates that don't really need the parse functions in them.

Another way to fix this is cut these pages into multiple pages, this of course has the issue of losing organization.

Obviously to make these pages work we don't want to cut any of the {{#varpull}}'s in the templates, so we need to find {{#if}}'s used for protecting from invalid data showing and remove them, and just trust people to input proper data.

Danxor (talk)17:01, 9 November 2012

Also on pages such as crew you can take various groupings of obtained such as

Decrypter's Armor (Proc Spawn) Flashheart's Nuclear Love Pants (Proc Spawn) Trendsetter's Boots (Proc Spawn)

And create this set as a single template that links to these 3 and put them on all the objects that use them... I know none of these solutions are ideal.

Danxor (talk)17:08, 9 November 2012

Basically what danxor said. If the problem gets to the point where we cannot maintain anymore then we need to look at some kind of extension.

Also minimizing the amount of formatting templates that are displayed helps too. There is a hard number of template expansions too. Which is the problem that LoH has on some of its larger card pages. I am considering removing some of the card text templates and just replacing with CSS

Zoycite (talk)04:58, 10 November 2012

Is there any way to force the wiki to render more {{#}}? That solution seems like the most obvious one.

I rewrote the raidlink template to use one less parser function. It seems to have cleared up some, but not all of the parser errors.

According to mediawiki, you can modify the expensive parser function limit:[1].

Klaxxin (talk)09:41, 10 November 2012

I tripled the default. I am a little paranoid about setting it too high since it does encourage a lot of nesting which is also bad.

Zoycite (talk)05:48, 11 November 2012

Thanks. That's cleared up the rendering problems on the item pages.

Klaxxin (talk)12:46, 11 November 2012