Site issue?... error messages on replies to posts

[jaggedfish]

I have been getting error messages on my last couple of post replies and wonder if anyone else has had these issues or if it is on my end? Nothing has changed on my end so suspect there may be a site issue.

When I click on the post button I get an error message then when I refresh it takes me back to the supposedly unsubmitted reply and says that there has been a post since I wrote my reply. Not actually correct. Can this be checked? Thanks!

Ian

[glenn]

Yes, it's an issue. It has happened to me multiple times over the weekend, as well as to two members I was PMing with. Funny thing is, the PMs send, even though you get an error message - result:several duplicate messages as the sender resends several times. .

[403delica]

Ditto! hope i did not post twice

[nxski]

I'm getting the same thing but only on my phone, not the computer.

[FalcoColumbarius]

Oh good... and I thought it was just me! I just received a PM in triplicate and I too have been getting the error reports over this past weekend or so. We had another issue take place recently where someone or thing was trying to crash the server which might be related to this error, I'll mention this to Mark, our enabler, who art in Lynn Valley...

If you do see this error message when you hit the submit button, my experience has been that the message has been posted but I haven't been redirected back into the thread. I "Ctrl C" anyway, just to be sure...

Falco.

P.S.: I notice it doesn't happen when I click the "Preview" button, only the "Submit" button. FC.

[mararmeisto]

Same trouble over here, on a desktop, a Mac at that, using Chrome for a browser.

[403delica]

Im getting error messages from tapatalk also

[dfnder]

I was going to blame tapatalk, it is almost as annoying as the error messages. They both really are :)$&@&$ pissIng me off.

Surprisingly I posted this with my phone and I got no error message.... could it be fixed?

[dfnder]

Well seems to be all gone as I have posted using both phone and comp and no issues.

[dfnder]

Haha I guess not... You can tell the threads which are suspect when you see double posts. I am thinking the problem arises only on certain threads. Possibly where it references prior posts and there is an error in one of them. Maybe if people made a post into the thread that they see the error message that would help track it down. This is strictly a guess btw

[FalcoColumbarius]

Yeah ~ it's still happening. Mark, this is the error message that I've been getting:

• "Warning: Unexpected character in input: ''' (ASCII=39) state=1 in /home/delica/public_html/forum/cache/queue.php on line 3
  
  Parse error: syntax error, unexpected ':' in /home/delica/public_html/forum/cache/queue.php on line 3"

[mark]

Thanks everybody for letting me know about this glitch.

We had some unplanned downtime (about two hours) late last week, and it appears that one of the cached files may have been corrupted. I have now cleared the cache, and have composed a few test posts (no errors yet).

Hopefully this has corrected the situation. However, if you experience a similar error after reading this, please let me know and I will take another look at this!


Mark

[mararmeisto]

Thanks everybody for letting me know about this glitch.

We had some unplanned downtime (about two hours) late last week, and it appears that one of the cached files may have been corrupted. I have now cleared the cache, and have composed a few test posts (no errors yet).

Hopefully this has corrected the situation. However, if you experience a similar error after reading this, please let me know and I will take another look at this!


Mark

Same error just now, in response to a different thread...

Addendum: although the error did not happen when responding to this post.

[FalcoColumbarius]

I've had the error report three times this morning, so far as well. Must be something else, Mark.

Falco.

[mark]

Shucks - Its always nice when the simplest fix turns out to be the one that works. However, this appears not to be the case this time (I managed to trigger the error myself, so I know that there still is an issue)...