CiviCRM Community Forums (archive)

Hello,

What do you people think about autosave in CiviMail once every two minutes or something similar.  People spend a lot of time composing emails in the wysiwyg editors and for whatever reason (user error, machine error, civi error) they loose their work.

Have had a couple of feedbacks recently from unhappy customers recently that lost 45 minutes of work due to some form of flakiness and hey, it can happen to the best of us, as anyone who has attended a book sprint will know.

I'm thinking about a simple ajax call every few minutes - something along the lines of what online email clients (gmail, etc.) do and am presuming that because they (as well as all office applications) use it as a to mitigate flakiness in the layers below and above, there shouldn't be too much disagreement about the wisdom of doing so for CiviCRM.

We have the resources (time / skills / money) to implement this (as long as it is reasonably straightforward) and commit to core.  What do you think? Good idea?

Michael

I'd be great, but several issues:

1) That's rather easy to do the ajax save IF there is an API. There isn't now, could it easily be added or that's not possible because of $*&! wizard ?

2) by saving periodically, means that the current draft is going to erase the existing version, ie. can't "undo" the last modification, even if I leave the page without saving it... or that if I screw the content badly 2 seconds before the autosave, then it's going to save it, over the ok content that was there 3 seconds ago, and can't cancel the last modifications.

X+