Autosave for any form

EXACTLY the same issue here. I'm not sure how complicated this is, but it would be huge.

Subscribing

Eric

I hear that and it's definitely a good thought.

If only I had control of my users! It is a business where they use ie7 for some reason and are change averse. I can't believe how difficult it is to get people to get browsers and particularly one that's not IE (particularly among older users). I'm sure this is a problem that many of us have.

Eric

subscribed

Just adding another vote for this feature. It's a great module - thanks for all the effort!

The way the Drupal 7 version of this module works, it *should* be possible to do. I tried to keep such extension in mind when updating it. I do not have bandwidth to work on such a feature myself, but would accept patches.

I think what you'd need to do is add another branch to hook_form_alter for the comment form, and then introduce a branch of some sort to autosave_restore() for nodes vs. comments. (I don't think it can be done entirely generically.) The rest is just hooking up settings in the UI and such.

That said, the *only* reason to do this with an AHAH callback is for dynamic forms. For any form that doesn't change its structure in response to user input (the way "add more" fields work), this should be done using localStorage instead, completely client side. Comments, of course, are now in that first category in Drupal 7. Bah. :-)

Attached patch creates a textarea on the admin/config/content/autosave form to add form_ids to apply autosave to.

The patch tampers with the html id of the autosaved form so it might brake some existing css.

I don't know what happens if there are several forms on the same page to autosave but it probably won't work.

This version removes the autosaved form on form submission.

Also, the patch from #2201317: autosave_node_presave() should be autosave_node_update() has been phased out.

Better and general handling of $form_state['build_info']['args']. (This is needed e.g. on entity forms.)

Also fixing autosaved form removal on form submit.

Previous patch works but has a huge security issue: the whole $form_state['build_info']['args'] array goes into the html. (Serialized, but still.)

So the proper way to do this is:
1. In autosave_form_alter() store $form_state['build_info']['args'] in the {autosaved_forms} db table in a new column (called 'args' for example).
2. In autosave_restore() $form_state['build_info']['args'] = $record->args;

Patch contains the suggested changes from the previous comment.

Changes relative to previous patch:

1. Introducing hook_autosave_prevent() to intervene the autosave process.
2. Form arguments are not saved in a restore process.

Added an autosave.api.php file to document hook_autosave_prevent().

Thanks for this patch. I've tested it a little with the weebform module and with a custom form and it works well.

Make forms autosaved before the update work after the update.

Fix hook_autosave_prevent_alter().
Committed.

How do I get this to work for comments? I would like to try it out. Where can I find instructions for how to configure the module?

@matt.rad Go to admin/config/content/autosave and add the form id of the form you want to autosave.

Thanks a lot. It works perfectly.

For anyone else who might benefit be wondering, the module Devel Form Debug was an easy way to find form IDs.