{{DISPLAYTITLE}} is not a template. See Help:Magic words
I'm getting ready to deploy a new {{trope}}/{{work}} template that makes submenus appear, so that if you have a pages like Star Trek: The Next Generation/Recap/S3/E1 The Best of Both Worlds, you get a menu like:
( Recap )| S1 » || S2 » || _S3 »_ | ( E1 The Best of Both Worlds )| S4 » | | E2 The one where they go to France || ... |Now, the main problem is that we don't have pages named exactly like that. I'm trying to decide if I want to rename them, or come up with some kind of hack to make it work with the spaced version in Recap.
Took a while to develop too, took some PHP code I found, translated it to Perl so I could think, and then retranslated it to Lua. After discovering it took 10 times longer to run, I kept messing around with minor optimizations -- until I realized that the slowdown was from using the unicode string library instead of byte-strings. Since the only string ops work on ASCII characters and passthrough the rest, I got rid of mw.ustring to get comparable speed to the earlier template. The difference here was only .10s to .01s, but you know, every page it adds up.
In other news, it looks like we might be moving to a new hosting company next week to improve stability. RamNode is dirt cheap but you get what you pay for.
-- ∇×V
I'm getting ready to deploy a new {{trope}}/{{work}} template that makes submenus appear, so that if you have a pages like Star Trek: The Next Generation/Recap/S3/E1 The Best of Both Worlds, you get a menu like:
( Recap )| S1 » || S2 » || _S3 »_ | ( E1 The Best of Both Worlds )| S4 » | | E2 The one where they go to France || ... |Now, the main problem is that we don't have pages named exactly like that. I'm trying to decide if I want to rename them, or come up with some kind of hack to make it work with the spaced version in Recap.
Took a while to develop too, took some PHP code I found, translated it to Perl so I could think, and then retranslated it to Lua. After discovering it took 10 times longer to run, I kept messing around with minor optimizations -- until I realized that the slowdown was from using the unicode string library instead of byte-strings. Since the only string ops work on ASCII characters and passthrough the rest, I got rid of mw.ustring to get comparable speed to the earlier template. The difference here was only .10s to .01s, but you know, every page it adds up.
In other news, it looks like we might be moving to a new hosting company next week to improve stability. RamNode is dirt cheap but you get what you pay for.
-- ∇×V