Please do not use this template. You can't tell the time to anything like the right minute using expressions like this. You're lucky to even get the right day. Doing this sort of rubbish just encourages the creation of "purge" links, which damage the efficiency of this site. -- Tim Starling 15:33, 20 April 2006 (UTC)
- I agree with Tim. --Uncle Ed 16:05, 20 April 2006 (UTC)
- Ok. I guess I was a bit unlucky in my testing (even whilst logged out) because I kept getting the right time - I had a vague idea that caching could foul things up but it appeared not to so I ploughed on - putting it on half-a-dozen pages or so to solicit feedback. Obviously now I've got that I happy to trash the current implementation on Tim's say so. However I do think having local time on location pages is a boon. Ed, do you too? If so we could consider an implementation for javascript-enabled users that doesn't bother the server. What do you think? [Pcb21 too lazy to log in]
- You have a stub threshold set, which disables the parser cache, that's probably why your testing gave you the wrong idea. I've been thinking about changing the output of {{CURRENTTIME}} so that it gives a <script> tag which will show the current time, down to ticking seconds. -- Tim Starling 01:17, 21 April 2006 (UTC)
- After I posted the above in a rush it did occur to me that CURRENTTIME and its cousins were probably useless in general because of caching (natural use-cases are going to be similar to what I did in structure), so I'd heartily approve of that if you decided to do it. Pcb21 Pete 07:28, 21 April 2006 (UTC)