An Important Update

Dear Followers Of This Blog ...

If you did not use a Blogger / Google account when you Followed this blog, years ago, you are probably not Following now . During the past...

Saturday, July 23, 2011

You Are Responsible For The Actions Of AutoSave, As You Publish A Post

All too often, we see a naive and plaintive request for help in Blogger Help Forum: Something Is Broken
I spent hours composing my post. Just before I published, I hit Ctrl-Z - and at that very same moment, AutoSave kicked in, and saved my empty post! Please get my post restored!!
This is yet one more request that can't be easily fulfilled.

If you, personally, are familiar with Ctrl-Z (Undo), you may also know about Ctrl-Y (Redo).

If you act immediately, you may be able to recover your work.
If you just un did everything in your post - and your work was unsaved - you may be able to re do everything. If, and only if, you act immediately - hit Ctrl-Y, then Save, to recover from your mistake.

If you just learned about your mistake, and you are now reading this post, the latter advice may not help you - this time. Just be prepared, if this happens to you, again.

Post Editor is not part of a Transaction Processing System.
Just as Blogger is not a Content Management System, the Blogger Post Editor is not based on a Transaction Processing System. It is simply not possible to restore blog posts to any given point in time, to reverse a mistake that you may have just made.

If you spend hours without Publishing your new post, and you lose what you've composed by saving an empty post, that's just like saving after you make any other mistake, large or small. Once you Save - either by hitting the button, or by letting AutoSave save for you, when you are composing a new post - what is Saved is what is now in the Draft copy of your unpublished post.

If this is not acceptable, write as much content as possible, publish, then edit.
If you cannot deal with the limitations of AutoSave and Post Editor, disable AutoSave as you compose a large post. As you compose, hit "Save As Draft" regularly - after you have published an initial stub copy of your new post. You may then decide - not AutoSave - when to save as Draft.

Dude, hit me with a comment!

D.B. Echo said...

The other option, of course, is one that a lot of people resorted to in the bad old days before AutoSave: compose your post offline in a text editor, then copy and paste it into a blog post. I've had a lot fewer "Blogger ate my homework" incidents since AutoSave was introduced.

bytehead said...

The real "fix" to this problem is extremely easy.

Yes, Control-Z will blank out your post (although I've noticed that in Gmail it works much, much differently...).

Control-Y will redo everything you've just blown away with Control-Z.

I just verified it, and it works as it should.

Sub-Radar-Mike said...

Yeah it made me feel a lot safer once autosave was put into place... plus it saves like every other second.

Jason said...

Sounds like the problem is Control-Z behavior (shouldn't it just undo a small, recent change, not delete your entire post?), not autosave.

I've seen the opposite problem in the new blogger editor---autosave wasn't working, I was not informed that it wasn't working and a accidental click closed my edit page tab without any confirmation that I really wanted to close the tab.

I'm becoming fond of DB Echo's idea of composing elsewhere...

a female Faust said...

@jason : same sort of experience -- is it me or does the (*&^%) new blogger interface austosave much less frequently? i have spent three times as long as it took me to compose trying to find somewhere my OS may have stashed it, to no avail. because i trusted blogger would save it. the save was halfway through, thus incomplete.

thanks for letting me kvetch. what i mean to say is: blogger is a wonderful service that i am sure does the bestg it can.....

a female Faust said...

compose then copy paste...

good idea- if your text editor saves --