The project page states:
If the user's browser or machine dies while editing a node; the edits will be presented to the user the next time they return to the node.

How about if Drupal dies while they are editing? Or the network connection?

Comments

liquidcms’s picture

liquidcms commented

or your house blows up, or power goes out, or...

Autosave saves copies of your form in the background.. it saves these to the database. once in the db, nothing outside of wherever your db is located has much impact.

liquidcms’s picture

liquidcms commented

ps - i really hope your house doesn't blow up.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

I wasn't trying to be smart. I didn't know where you saved the backup and that could make a difference.

I am dragging my feet about installing this feature because my users, while normally intelligent, seem to get stupid when they sit in front of the new Drupal site. Is the back up interval configurable? I assume that AJAX issues a request to the site to make the copy, so the user should know at that point that something is amiss?

liquidcms’s picture

liquidcms commented

interval is configurable.

there is a small "popup" at the bottom of the screen each time the save is triggered (popup can be disabled)

not sure what you mean by amiss - nothing is broken when the autosave cuts in

best bet is to try it out.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Thanks.

The reason the customer is interested in this is because one of the analysts worked for two hours on a post and when he hit "Submit" the site was down and he lost everything. In that case there would be no database to save into, but if there had been an interim error message (e.g. from autosave), he would at least know to copy it somewhere else or not hit submit yet.

liquidcms’s picture

liquidcms commented

hmm.. interesting use case - so you are saying they began an edit session, immediately after the web server or mysql server crashed.. but user would have no way to know that so they continues to edit on the form no realizing the site was gone?

interesting - someone would need to test.. conceivably there is an error msg returned from the ajax call but likely not anything too informative - wouldn't be a bad thing to be able to support.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Yes, it was something like that. And the user (who is a bit arrogant) was quite upset at the loss of his work. Why he doesn't compose in Word, I have no idea, but that's his call.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Well, I have tried the module and it is clearly not ready for CKEditor without WYSIWYG. I am abandoning this for now.

liquidcms’s picture

liquidcms commented

Yes, not sure how i haven't made that clear enough on the project page - Autosave only works with WYSIWYG

but CK works with Autosave.. so shouldn't be a big stretch - for them; not me.. :)

liquidcms’s picture

liquidcms commented
Status: Active » Postponed

likely a few months out before my client will want to fund adding this feature as we aren't using the module until then.

but if anyone provides a patch i will gladly commit it