I have committed a Parse Error!

Apparently, there are parse errors in my attempt to view replies to my thread posts. Not that anything I said was worth reading, let alone respond to...

Techies?

You're parsing wrong, silly. Do it right next time.

Seems you have a multitude of difficulties.

originally posted by: Phage
You're parsing wrong, silly. Do it right next time.

Seems you have a multitude of difficulties.

He Has Spoken !!!!!!!!!!!

a reply to: Ultralight
It's those adverbs. They get you every time.

a reply to: Phage

Don't we all?

a reply to: Kapusta

The error code literally says "parse error"(424)

a reply to: Ultralight
Another oddity I've just noticed.
This reply to Kapusta appears on the list of replies to my own posts.
I doubt that you went to the trouble of editing out my name, so it looks as though it got re-directed somehow.

a reply to: Ultralight

Were you trying to 'parse' yourself off as someone else !??

a reply to: Ultralight

It did that when I was checking messages, too. Then it just started working. Weird.

It might have something to do with the recent server migration, I know they were changing some of the coding too. Although the smilies ...they never changed!

a reply to: Timely

Hard to do considering my avatar is me. But thanks for the chuckle!

Parsing is how the virtual code is assembled and executed in accordance with the server and the client(You, or more precisely, your browser).

Most of the time Parse errors are a communications breakdown between the browser and the the server, a piece of code was not interpreted correctly, or a value was attributed to a function in the code that does not exist.

Clearing your cookies might help as some of these errors are user generated. If that doesn't solve the problem for you then it isn't a parsing error generated from your browser but from the server itself.

ATS just conducted a server migration. Errors like these are likely to continue popping up until all the bugs are worked out.