I think "forn_autosave" or "autosave_form" or using "autosave" itself (assuming current maintainer agrees), is a better title, as its not just node's that this module can support.
I think "forn_autosave" or "autosave_form" or using "autosave" itself (assuming current maintainer agrees), is a better title, as its not just node's that this module can support.
Comments
Comment #1
zhgenti commentedMerging it with autosave module probably will not work. As long as maintainers seem to be not interested in it #1280840: Modernize for Drupal 7
So I think making it work for any form, but not only for nodes, and call it "form_autosave" might be useful. I'm not sure there is an easy way to make it work for custom forms created with FormsAPI or modules like webform. But I will look into it in more details a bit later.
Comment #2
jason.fisher commentedI agree. I like the generalized approach of saving the form state instead of field states -- that seems helpful for avoiding validation issues without needing to resort to things like the required_for_pub module. (http://drupal.org/project/required_for_pub)
Comment #3
Patribus commentedhello: is the development of this module still active?
thanks