@ethitter
13 years, 2 months ago
The site isn’t using any caching right now, which is part of why this error perplexes me so much.
I’m beginning to suspect some caching-related things changed between WP 2.9.2 and 3.0, because I didn’t have this problem prior to upgrading.
