SuzyUK - 10:54 pm on Jul 5, 2011 (gmt 0)
alt, I agree the meta may not be a complete "fix", (in my defence, I did add troubleshooting) - it could be that if IE8 is forced it will break something else on the site - I think you were likely close with your original observation about CMS themes.
just remove the server configuration instead.
Easier said than done maybe, unless you're a theme fixer guru :) did you see the OP was using the Thesis WP theme? just try a search for Thesis, WordPress and emulate IE7.. (and be horrified at the "easy fix" being built into WP themes and lines of code given out on WP forums :o)
It's quite possible that the header is built into an ajax/admin.php (or some such template file) as a fix for the theme version. Paid themes are notoriously difficult to troubleshoot especially if there's been some tweaking going on. - and then if a theme version is only supported via upgrade then there is no need to keep the old version future compatible so no harm in the meta header, in theory
I don't think it's the actual server httpd.conf (or whatever Apache file) as I checked some other sites on the IP and they're not affected, but the actual configuration could depend on the level of edit privileges an author has so it's still a possibility - I do think it could be the WP theme, or some amendment to it?
it's very often quicker, easier to use the brute force method, kind of like CSS specificity overrides, instead of trying to find the needle in the haystack ;)
Guess work really, but interesting (and btw stop thinking like me haha!)