Hard to tell without seeing it. Could be just browser caching.

Thanks for your PM. Unfortunately, my post count is not high enough to allow sending PMs. Here's my reply:

No, it's not fine. What you're missing is a reference to your style sheet: hxxp://yourdomain.com/blog/wp-content/themes/elegant-grunge/style.css

Check your header.php template file to make sure it's there and that it's not excluded with some conditional rule. Alternatively PM me the contents of your header.php and I will take a look.

OK, I'm not quite sure.

Did you do any changes to the header.php as compared to the original theme? If yes, try re-uploading the original file. If not, the only thought is that the latest version of WP (I see you upgraded to 3.1.2) is not playing well with your theme.

To fix it, I would try deleting the following line from your header.php:

This will cause the custom favicon to disappear, but otherwise the theme should work fine (hopefully). Alternatively, you can move the above line below your stylesheet reference, like so:

Let me know how it went, but pls don't PM as I cannot reply. Thanks!

Edit: One more possibility: is it possible that you deleted or messed up the elegant_grunge_the_favicon function from your functions.php? If yes, try reinserting it from the original theme file.

Tried commenting it out and then removing it, but still no luck

I cant understand it, as far as i know all i did was auto upgrade the cache today, and im guessing thats when the problem started, but cant be sure

Have tried manually putting the stylesheet line in

<link rel="stylesheet" href="**myblog.com**/blog/wp-content/themes/elegant-grunge/style.css" type="text/css" media="screen" />

but it seems to ignore it and somehow remove it when processing

One last thought... try turning off your plugins. If the theme works fine with all plugins turned off, start turning them on, one by one and check after each new plugin. Make sure you are clearing your cache after each try.

Think i finally stumbled on the solution -- for some reason the w3 total cache minify of css was causing problems, so disabled that particular feature and its working again

Glad you got it solved!