Thanks for the props folks but the fact is, I didn't do anything to fix this issue. By the time I found out it was occurring it seemed to have disappeared. That concerns me as much as the problem itself. We've encountered the same issue in the past on a few occasions. In those instances the issue was created because someone pasted code from another website, or some other garbage code, into an article or module that was published to the frontpage.
The problem came from code snippets contained in those pasted content items that were looking for HTML, CSS, Javascript and/or PHP files they couldn't find -- because what they were looking for was located on their original servers and not here, or because the code just stunk. This will absolutely stop Microsoft browsers in their tracks. For you guys, my recommendation on that is the same as Roy's, if you use IE, get something else and preferably Firefox. You won't have these problems.
On this side of things, I randomly checked three articles published in the last 48 hours and found that all three had garbage code in them introduced by their authors. I won't mention any names except that they're not Steve or FLCeltsFan. My suspicion is that someone posted something that wrecked the place, didn't realize it for awhile, then unpublished the thing when they did -- and didn't mention a thing about it to anyone. That's the way authors are you know. They're sneaky.
I preach [slams right knife hand into left open palm], and preach [slams right knife hand into left open palm again], and preach [slams right knife hand into left open palm yet a third time]. All it accomplishes is that authors behave themselves for about a week before they revert back to their true natures. It's like trying to herd cats. There are, like the aforementioned, pristine exceptions of course but otherwise, what's a poor webmaster to do?
Anyway, I'm sure the culprit is skulking around somewhere fully aware of his sin. We'll let it go this time as a warning. In the future though, if this happens again, any of you who are robbed of access here make lots of notes about it -- everything you can think of. Those of you who still has access when that takes place, make notes on what went down and when, who wrote/published what article on the frontpage of the site. Together we'll hunt down that criminal and drag him from the seedy bowels of this place into good old-fashioned light of CelticsBlog justice.