Template talk:Colored Link

This template makes links show in the desired color.

First parameter is the text to display, second parameter is a named parameter "color" which has a hex value: FFFFFF, 343434, FFBB55, etc.  - BBR  talk / cont 03:48, 6 August 2007 (PDT)

I give up, I dunno what's going on here. It seems the updates I'm making to this page are only being enforced randomly. I got the Necro Spell template to appear correctly on one page load, then on the next page load (with no further edits) it goes back to showing {{{2}}} again.

Suspect a cache issue of some sort, but I think it's all good in the current revision.

- Bomb Bloke 06:22, 11 November 2008 (UTC)

From what I can tell some people started using the template bypassing one of the parameters. Instead of inputting the page name and title, they just did the page name. If you update the templates which use ColoredLink then it will work again. For example ColoredLink|Wither|color=ffffff becomes ColoredLink|Wither|Wither|color=ffffff - JC the Builder 06:45, 11 November 2008 (UTC)

The template was supposed to allow people to bypass that parameter, but something in the wiki update deprecated the code it was using to check whether it was there or not.

Anyway, my caching issue seems to have gone now and I see my edits worked (that is to say, you can once again use "ColoredLink|Wither|color=ffffff" or "ColoredLink|Wither|Wither|color=ffffff").

- Bomb Bloke 07:45, 11 November 2008 (UTC)

If you ever look on the Special:Statistics page, you will see the line "The job queue length is 0." Every time you edit a template that is used on many pages the server backend has to recursively fix each of those pages, so it sticks them all in the job queue. The queue is hardly ever greater than 0 because hardly anybody edits templates around here. I've sent it up to a few hundred a few times when making edits to the Creature Template, but that's about as high as it's ever been.
When you change a template and then look at one of the pages that implements the template, it's a crap shoot whether or not that page will happen to be near the head of the job queue or near the tail. So, long story short, yeah, it's pretty much a caching issue. --Cogniac 00:47, 13 November 2008 (UTC)

Ah, I'd been wondering what the "job queue" thingy was. Thanks for the tip. :) - Bomb Bloke 06:53, 13 November 2008 (UTC)