lazyliteratus posted an update 12 years, 2 months ago
Livid beyond words. An entire 900-word Tea Trade blog vanished the MOMENT I tried to save it. There’s no recovering the text from prior saves or anything. Not sure what happened…but I’m pissed.
Darn, and we were not even able to read it. 🙁
Experiences like this in the past are he reason why I write (large) text in a text editor like Notepad++ and not in a web-editor.
(And for some reason the first version of this reply disappeared too)
That’s what I usually do. I write it in Word then port out to the blog. That wasn’t an option this time because I was on a slow computer. Unfortunately, it never autosaved.
Looking into this to see if I can recreate the problem. @lazyliteratus no revisions were saved by the autosave, it appears. Did you hit save as draft while writing at all, or go straight to Publish?
I just tested this too @peter – Autosave saves a blog post every minute as you write! I hit “publish” without first saving as a draft, but it’s not necessary to save as a draft, because like I said, it’s set to saving every 60 seconds.
I was typing it directly into the text editor. First time I’ve ever done way. It never gave me an option to autosave. I did try to save manually when I went to edit, but the text just vanished.
Okay, I’ve tested this thoroughly and have been unable to recreate it. I started a post in your blog to be sure (just in case there was something specifically wrong with your blog somehow) and the autosave worked perfectly. As soon as I started typing in the editor the autosave created the first draft. I then force closed my browser without saving to simulate a crash, when I went back in everything was there. As jackie said, autosave is currently configured to save every 60 seconds as you type. Note, however, that autosave does not work if you are typing in the HTML editor. That should not be the case because I’ve programmed it to load the Visual editor by default, if you were typing in HTML, then you may have clicked that tab inadvertently.
On the troubleshooting side that leaves us with a conflict with your computer somehow which prevented the autoave from working (it requires javascript, which can conflict and not work sometimes). This could depend on the web browser (the version is important too, if you are using IE, you should be using IE9), and your operating system. Not all part of things around here are guaranteed to work in older browsers. I know for a fact that certain things do not work in IE8. I use and recommend Google Chrome first and FireFox second. I cannot bring myself to endorse any other browser. I tested your site in Windows and Ubuntu, Jackie tested it in Mac.
It may have just been an anomaly. If you are using FireFox, try not to keep too many tabs open (FireFox bleeds memory, lots of tabs can cause problems). Chrome is more forgiving with lots of tabs because of how it handles them technically. When memory gets low, websites can cease to function. Also, clear the browser cache, that’s another trick to do when things get funny.
I am really sorry that you lost your post. I can certainly sympathize, I lost a 1000-word essay for one of my classes last week (in my case it was totally my fault because I was careless), but that horrible feeling of work lost is still pretty lousy. I’m hoping that it’s something we don’t experience much around here.
First off, I’m sorry I made this an update instead of a private message. I’ve never lost a blog quite like that. I’m also sorry that @Peter had to troubleshoot it for so long. It was an older computer, and script for the website kept failing in the browser. That and I was updating in HTML. So, that explains a lot. I’ll just do the copy/paste method. Thanks all.
Darn, and we were not even able to read it. 🙁
Experiences like this in the past are he reason why I write (large) text in a text editor like Notepad++ and not in a web-editor.
(And for some reason the first version of this reply disappeared too)
That’s what I usually do. I write it in Word then port out to the blog. That wasn’t an option this time because I was on a slow computer. Unfortunately, it never autosaved.
Looking into this to see if I can recreate the problem. @lazyliteratus no revisions were saved by the autosave, it appears. Did you hit save as draft while writing at all, or go straight to Publish?
I just tested this too @peter – Autosave saves a blog post every minute as you write! I hit “publish” without first saving as a draft, but it’s not necessary to save as a draft, because like I said, it’s set to saving every 60 seconds.
I was typing it directly into the text editor. First time I’ve ever done way. It never gave me an option to autosave. I did try to save manually when I went to edit, but the text just vanished.
Okay, I’ve tested this thoroughly and have been unable to recreate it. I started a post in your blog to be sure (just in case there was something specifically wrong with your blog somehow) and the autosave worked perfectly. As soon as I started typing in the editor the autosave created the first draft. I then force closed my browser without saving to simulate a crash, when I went back in everything was there. As jackie said, autosave is currently configured to save every 60 seconds as you type. Note, however, that autosave does not work if you are typing in the HTML editor. That should not be the case because I’ve programmed it to load the Visual editor by default, if you were typing in HTML, then you may have clicked that tab inadvertently.
On the troubleshooting side that leaves us with a conflict with your computer somehow which prevented the autoave from working (it requires javascript, which can conflict and not work sometimes). This could depend on the web browser (the version is important too, if you are using IE, you should be using IE9), and your operating system. Not all part of things around here are guaranteed to work in older browsers. I know for a fact that certain things do not work in IE8. I use and recommend Google Chrome first and FireFox second. I cannot bring myself to endorse any other browser. I tested your site in Windows and Ubuntu, Jackie tested it in Mac.
It may have just been an anomaly. If you are using FireFox, try not to keep too many tabs open (FireFox bleeds memory, lots of tabs can cause problems). Chrome is more forgiving with lots of tabs because of how it handles them technically. When memory gets low, websites can cease to function. Also, clear the browser cache, that’s another trick to do when things get funny.
I am really sorry that you lost your post. I can certainly sympathize, I lost a 1000-word essay for one of my classes last week (in my case it was totally my fault because I was careless), but that horrible feeling of work lost is still pretty lousy. I’m hoping that it’s something we don’t experience much around here.
First off, I’m sorry I made this an update instead of a private message. I’ve never lost a blog quite like that. I’m also sorry that @Peter had to troubleshoot it for so long. It was an older computer, and script for the website kept failing in the browser. That and I was updating in HTML. So, that explains a lot. I’ll just do the copy/paste method. Thanks all.
Lost a blog, have a tea?
Sage words.
Well, I did write one that was acceptable.