Impressive-looking posting error

[somegirl]

I was trying to post a reply to TOSAT and got this:

[ducpainter]

That's pretty cool.   

With or without quote?

[somegirl]

No quote.

[ducpainter]

No quote.

calling the webgeeks....

[sqweak]

that's a buncha javascript.  got me. Daryl?

[Speeddog]

msincredible, making SMF swear like a drunken sailor gets you nominated for troublemaker of the month.

Either that or it's your browser swearing.

[darylbowden]

All I can tell you is that is some seriously obfuscated javascript right there.  It's actually trying to perform some kind of AJAX function as it's showing a XMLHttpRequest() object.  However, why it showed up on the end users screen I have no idea.

ms, can you report browser/OS with versions?

[darylbowden]

I think the real issue is that for some odd reason SMF echoed the Javascript file instead of actually loading it through that echo.  I would guess it was some kind of fluke browser parsing error that did that, but we should obviously keep an eye on it to see if it happens again...

[duccarlos]

It's a browser issue. You should be able to get through it by simply clearing your cache. If you've never done this and you're using Internet Explorer, you should close all your browsers, go to the Control Panel and select Internet Options. In the newer version you'll see a Delete button on the Browsing History. Delete the first 3 options.

[somegirl]

Thanks guys, I am using Firefox 2.0.0.11 and Windows XP, nothing exotic.  I have it set to automatically clear the cache each time I end a session.

msincredible, making SMF swear like a drunken sailor gets you nominated for troublemaker of the month.

Oooh, I get to be the first!

[darylbowden]

It's a browser issue. You should be able to get through it by simply clearing your cache. If you've never done this and you're using Internet Explorer, you should close all your browsers, go to the Control Panel and select Internet Options. In the newer version you'll see a Delete button on the Browsing History. Delete the first 3 options.

That would cure the symptom, not the problem.  The problem here is that for some reason SMF echoed out the JavaScript source code and instead of it being loaded into memory, it was displayed on the screen.  

[Speeddog]

Perhaps we can approach this as an isolated intarwebz spasm, and if it happens again, try to track it down?

msincredible, did this happen just once, or is it repeating?

[somegirl]

So far it was a one-time event.  I also think we should wait on troubleshooting it.