Hi Jimmy - Please don't say the word famous.. I get very embarrassed by this.. . Perhaps talkative is a better description. I can proudly wear that one when it comes to DNN! (just ask my kids)
NOW I KNOW what you're talking about - amazing when you get all the facts isn't.
Ok yes I know what that will be - comment out the language selector it wasn't in the 3.013 build and if you look at your logs you will probably see an error regarding to it. If I'm correct, I believe it was the 3.1+ build that had the localisation and skins coming out after that which had languages code in it didn't work.
By default if there is a problem with a skin, then it reverts back to the default blue skin. But I'm surprised your other pages didnt' come up with error to alert you.
You should at the very least upgrad to 3.1.1 or 3.2.2 - DNN4, I think at this exact date - might still require work to get extra modules running. I believe that 3.2.2 /latest 3 build is regarded as the most stable.
People are only updating to 4 if they require developing in the VS2005/SQL 2005 environment on the aspnet 2 platform.
While some people have upgraded, I'd be taking lots of backups first..
Now I think we need to ask a few more questions to give people the answers they need.
Anyway for now - check the languages and check the search perhaps - and remove those tokens and refresh the skins.
Nina Meiers