Guess I should have done a search for it before posting it. But I was a bit busy clobbering the spammers... ;P
Richard Deeming wrote:
Chris said it was a caching issue, kicked the cache, and marked the bug as fixed. Unfortunately, the fix didn't last.
I guess Chris will kick it a bit harder soon enough. It's not a high priority bug, just figured I'd let the hamster masters know :)
Tom