| Attribute | Average |
|---|---|
| Features | 2.5 / 5 |
| Reliability | 3.5 / 5 |
| Ease Of Use | 3.5 / 5 |
| Documentation | 4 / 5 |
| Vote Count | 2 |
The Autosave module automatically saves a snapshot of your content type form using AJAX. 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. The user may toggle back and forth between the last saved version and the... [More...]
| Maintainer: | Crell |
| Links: | |
| Categories: | Content, Utility |
| Version | Date | Files | Release notes |
|---|---|---|---|
| 6.x-2.9 | 2010-Dec-09 | Download | Recommended |
| 5.x-3.2 | 2008-Jul-20 | Download | Recommended |
| 7.x-1.x-dev | 2011-Mar-14 | Download | Development |
| 6.x-2.x-dev | 2011-Mar-04 | Download | Development |
Options: Add a review
Doesn't work with FCKEditor. A message appears on the bottom of the screen that the form was saved, but clicking "View" does nothing. A javascript error in jquery.field.js on 648.
After install, go to each content type to enable:
http://localhost/admin/content/types
(Autosave 5.x-3.1)
(FCKeditor 5.x-2.1)
If you are actually writing content online, the Autosave module can be a lifesaver for you. When you type a good solid text (which hasn't necessarily have to be very long), chances are you hit some Back or Reload shortcut sooner or later.
Autosave let's you determine the amount of time between each save. This save is done in a temporal table, so the document is not immediately updated. When you accidentally or intentionally leave the node you are editing and get back to it, hours or days later, you get notified changes were made and offered a choice to view them or ignore them. When you view the previous changes, the editable text show additional changes. You then get to choose to keep, ignore or reset these changes.
Notifications are done with an unobtrusive pop up layer, 1 line in height, extended over the full width of the view port at the bottom. The position of this layer cannot be configured however. People with smaller resolutions might find the layer overlapping their editable region, which may be uncomfortable. Colors and fonts are also non-configurable.
It is possible to set Autosave per content type, in the content type properties. As with many Drupal modules, this means configurable options are in two (or more) places, namely the content types properties page and the module's own configuration page. I would suggest to all modules to intuitively implement such options on both pages.
Documentation (I am reviewing the README) is small, but all that you need for a module of this kind.
Byelex | Imre Gmelig Meijling | Netwatmeer.nl
