Regardless of where I ask this question the only answer that is ever received is:
please start your own thread per:
Closing this because the issue was resolved for the OP.
Great, except most of the people that I know that claim to have resolved this "INTERMITTENT" problem haven't really resolved it, they have merely not had it occur for a brief period of time.
This is an Intermittent problem and it is therefore impossible to declare it resolved in any small window of time. I have gone periods without having this error come up, and I have had it come up fairly frequently with no document-able reason for it.
This problem did not exist at all prior to the wordpress 3.6 updates..
So, let me re-post my message, in a new thread as ordered, and oen that I hope will remain open until an actual explanation for the problem and a resolution are forthcoming...
Common Error Message:Connection lost. Saving has been disabled until you’re reconnected. We’re backing up this post in your browser, just in case.
Common Problem... perhaps system wide...
Okay, so now we have been told that since every system is different and as a result every problem is different.
We have been told that there is no system wide fix because there is no system wide problems...
If that is the case, then please explain why EVERY one of the 500+ word press sites that we own, operate or manage for clients expresses this same, exact error AFTER each was upgraded to WP 3.60?
We have sites running themes from virtually every theme creator.
We are running sites using a total of over 300 different plugins, with different groups of plugins in different sites...
We are running sites on shared hosting accounts, VPS accounts and a variety of different dedicated servers with some using rotating memory and some solid state drives...
We are using different hosting services from Liquid Web, to network solutions, to GoDaddy, to HostGator, to blue host, to 1&1, and others...
THE ONLY COMMON DENOMINATOR HAS BEE THE UPGRADE TO WP 3.6!!!!
I can only conclude that if it walks like a duck, sounds like a duck, smells like a duck... then it is probably a duck!!!
Now instead of telling people to open new threads based on some mis-conceived notion that this is not a system level problem, how about actually looking into the problem and being helpful rather than simply trying so hard to sweep this huge and growing problem under the rug in typical sysadmin style???
We are wasting HOURS every week screwing around waiting for this stupid issue to resolve itself so that we can proceed with our work.
Don't you get it, YOUR credibility is at stake on this issue, not mine!!!