Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The documentation link on the project's page points to http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/autosave/RE..., which is an old version of the documentation that states that autosaves are stored as revisions. This is no longer true.
You might want to point the link to the HEAD version http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/autosave/RE..., although what is true for HEAD might not always stand for all of the supported releases.
Comments
Comment #1
David Lesieur CreditAttribution: David Lesieur commentedAlso, the project page mentions that the jQuery Form Plugin is required. That does not seem true. At least the module works for me without that plugin.
Comment #2
liquidcms CreditAttribution: liquidcms commentedpretty sure it used to be required.. so possibly you have a newer version of jquery and form plugin is included in that??
Comment #3
David Lesieur CreditAttribution: David Lesieur commentedI'm using jQuery 1.2.6, but I guess the code might have changed enough that the plugin is no longer needed... I can't find any use of the Form Plugin's functions in Autosave. The Field plugin is still used though (and included in Autosave).
Comment #4
cedeweyThe documentation link is still broken. Here is the relevant installation and configuration information for the module. If someone can just create a quick page to this content, that should fix the documentation issue.
Thanks!
Clayton
DESCRIPTION
===========
The Autosave module automatically saves a node after a period of time. Content types that can be autosaved as well as the
period of time a node is autosaved, is configurable.
Autosaved nodes are saved as a snap shot of the form.
NOTE: this version of autosave only works for single form (of selected node type) on a page.
DEPENDENCIES
============
None
INSTALLATION
============
1. Place the "autosave" folder in your "modules" directory (i.e. modules/autosave).
2. Enable the Autosave module under Administer >> Site building >> Modules.
3. Under config for a node type select it to use Autosave.
4. Under Admin >> Site Config >> Autosave enter the period of time before each autosave (in milliseconds).
5. Enable autosave for the content types you wish it to run on ie:- Admin >> Structure >> Content Types >> Article >> Edit (located under the Publishing Options section)
IGNORE: means to ignore that there is an AUTOSAVED version and take the version that was last SUBMITTED, i.e. forget that the popup is telling you there was an Autosaved version and take what you currently see on the screen (which is the current rev stored in node table)
VIEW: will load the AUTOSAVED version that the popup is informing you exists
if you have selected VIEW you get:
RESET: takes you back to previous view, i.e. initial edit view, i.e. last submitted version, i.e the one in the node table
IGNORE: same as above
KEEP: keep the AUTOSAVED version and begin editing from that copy - NOTE: hasn't been submitted yet so STILL does not exist in the node table.
*Note: The Drupal 7 version only supports TinyMCE right now.