HeathGCF

Hi and thanks for the reply.

Now the NextScripts site is back up, I’ve raised a support ticket with all the relevant information I can provide in further detail.

Looking forward to getting to the bottom of this and thanks again.

Heath

I’m sorry, but that’s a poor and blasé response at best. Let’s turn that around shall we?

Out of over 6.8 million downloads, what percentage of those people have registered with and use the forums?

See my point? It’s a problem, no matter how theoretically small it might seem to you, that sufficiently enough people have bothered to raise. Granted, there’s a good chance that a huge majority of users who work on their sites for one or two posts, or short periods of time, aren’t ever likely to encounter this problem, even though it’s there.

Those who are spending most time working on their sites, posting larger volumes of content, seem to be those noticing it most. I guess it’s like anything though. Stare at something long enough, you’ll find some problem or another.

The issue still remains and as yet, the best answer I have found to the problem at hand, has been to roll back to 3.5 and *puff* the problem goes. Doesn’t that strike anyone as being somewhat coincidental?

Unfortunately, if there’s no actual solution to a problem that is genuinely there since 3.6 (no matter what percentages you want to throw around), pointing people in the direction of additional ways to waste hours of their lives on a wild goose chase, isn’t the most helpful.

My humble recommendation to ctabor, is therefore the following link, where 3.5 can be downloaded to roll back to…

https://www.ads-software.com/download/release-archive/ (for all release versions)

In reply to the answer above, that’s not strictly true.

This problem originated with the introduction of the autosave “feature” and is a commonly reported problem. It is indeed a WordPress problem, that triggers multiple requests to host servers, that their software rejects.

Report this as a host problem, I guarantee they will tell you it’s a WordPress problem and indeed, they’re right.

The vast majority of users reporting this very same issue, are either forced to roll back to 3.5 or sadly, await either a working autosave “feature” that doesn’t cause this issue, or the option to turn it off.

I run a site publishing 40-50 articles per day. When the problem first appeared with 3.6 we went through the process of stripping away all the plugins we use and testing thoroughly. The problem was still there. We’ve done the same with each new update and guess what… The problem is STILL there.

We love WordPress, but the sooner this problem is acknowledged for what it is and it’s either fixed or the autosave function is made an “optional feature” we can switch on/off, there’ll be countless more threads like this one, every day, going around in circles.

Apologies for the rant, but when I’m working 16 hours on a very busy site, losing as much as 15 minute per hour because of the “lost connection” problem, it gets more than tiresome…