replying to thread problems

[noblemacaw]

This has happened to me twice so far and I am not sure as to why it happens.

I been having problems posting replies in a thread I had created. Example is people have responded to my thread and I want to respond also but after writing up my response when I click submit it says I don't have the right to post. I end up having to save my work log out then log back in, past back in the content I wrote and THEN it allows me to submit my reply.

Is this due to the post being too long? Why do I loose the right to reply when I am still logged in? Is there something I need to be doing differently? Is there a word limit to a reply post?

I don't know if anyone else has this problem or had it happen to them. Next time it happens I will write down the exact error message I get.

Thank you for your assistance.

[Honesty]

Rebecca, I will ask Tony to have a look at this. I am not sure why it is happening, I do know it is not anything to do with your post being too long though! We will get back to shortly on this :)

[plax]

Rebecca- exactly when did this last occur? And did it only occur in a particular thread? The character limit per post is currently 15,000 characters. I'm sure you didn't exceed that limit.

[Mare]

This was an issue with me, too. Sometimes, I take awhile to finish with a thread and if it took too long, it wouldn't post. It was frustrating because sometimes I would lose everything I wrote down. I, also, learned to copy, then re-open so I could paste. It hasn't been so bad, lately, it seems I have more time to get it done. I just thought this was normal?

[plax]

This was an issue with me, too. Sometimes, I take awhile to finish with a thread and if it took too long, it wouldn't post. It was frustrating because sometimes I would lose everything I wrote down. I, also, learned to copy, then re-open so I could paste. It hasn't been so bad, lately, it seems I have more time to get it done. I just thought this was normal?Mare- I'm guessing what you're describing is those situations in which after hitting the submit button you get a long hanging period followed by a popup dialog that asks whether you wish to leave the page or remain on the page. Is this what you're describing? If so, I think it's different from what Rebecca has posted about.

[Mare]

No, it wasn't that, Tony. It said something more along the lines of having to re-fresh. It has happened to me even since I've discovered how to re-fresh and the re-fresh button didn't help, I had to close and then log on again.

[noblemacaw]

Mare has described very well what I was trying to convey in my OP. I do have the keep me log in checked so my session won't expire but I still experienced the problem I described and Mare has elaborated on.

[plax]

It sounds like you are both talking about the white 'no server connection' pages that recommend a manual page refresh to try and reestablish connection with the server. Is this correct? When you land on one of those pages that's titled "Database Error", it means the server was inadvertently rebooted and the database engine requires a restart. Unfortunately, we've experienced a few of those inadvertent server reboots during the past 3 weeks (or so). One occurred on 3/27, and another on 3/29, and yet another on 4/8. They were caused by a data center backup power system issue. That issue should now be resolved.

[Mare]

Hmm..I don't recall a 'no server connection' read. When or if it happens to me again, I'll write down exactly what it reads and get back to you.

[plax]

Hmm..I don't recall a 'no server connection' read. When or if it happens to me again, I'll write down exactly what it reads and get back to you.Sorry for being unclear. The 'no server connection' is not displayed on the white pages I've described. They may be titled with some form of 'page cannot be found' or similar message, or you will often see "404" or another failure code in the title. And they typically have a refresh link somewhere in the text next to a statement recommending an attempt at refreshing the page.

Here is a short list of server connection failure/page loading failure codes that you may see:


HTTP Status Codes
CODE INDICATION
2xx Success
200 OK - the request was fulfilled.
201 OK - following a POST command.
202 OK - accepted for processing, but processing is not completed.
203 OK - partial information--the returned information is only partial.
204 OK - no response--request received but no information exists to send back.
3xx Redirection
301 Moved - the data requested has a new location and the change is permanent.
302 Found - the data requested has a different URL temporarily.
303 Method - under discussion, a suggestion for the client to try another location.
304 Not Modified - the document has not been modified as expected.
4xx Error seems to be in the client
400 Bad request - syntax problem in the request or it could not be satisfied.
401 Unauthorized - the client is not authorized to access data.
402 Payment required - indicates a charging scheme is in effect.
403 Forbidden - access not required even with authorization.
404 Not found - server could not find the given resource.
5xx Error seems to be in the server
500 Internal Error - the server could not fulfill the request because of an unexpected condition.
501 Not implemented - the sever does not support the facility requested.
502 Server overloaded - high load (or servicing) in progress.
503 Gateway timeout - server waited for another service that did not complete in time.