can't enable the autosave feature

under the config for a node type, in the workflow section, is there not a checkbox that says: "Enable Autosave to add/edit forms for this node type" ?

I have this same problem too.

What is the "Workflow" section. From a google search, "workflow" is a whole other module. I am not sure if understand these directions.

Thanks

Okay I did find a work flow section, but I don't see where the nodes are being "autosaved". I don't see any options except the amount of intervals between save. Is there a way to have a user specify where it will be saved and where they can retrieve it later or something to that effect?

EDIT: I did notice the little pop up that comes on the bottom of the screen. That looks really cool.

However, it would be great to have more options like a location of the autosaves, a list of the autosaves, etc. That way a user can post more than one blog entry at a time and have separate autosaves for them.

I would try to code it myself, but I don't know anything about PHP. I have a book coming in the mail but I'm pretty useless for now.

-Thanks
BigSend
http://bigsendworld.com

does this require the workflow module? I can't seem to find the tab for enabling autosave for particular content types.

nope, nothing to do with workflow module.. but sadly, drupal core has named the section where you config a specific node type as workflow

not sure why this has been so confusing.. do people really not know how to get to the admin page to config a node type?? go to /admin/content/types

you should see a list of all your node types - pick one. On this form there should be a section called "Workflow" and under that there should be a checkbox to enable autosave for that type. If there isn't, try enabling the module. :)

re #5 - bigsend, no idea what you are talking about - what is "location of autosaves", what is "list of autosaves" - are you sugegsting that you have multiple browser windows open ADDING multiple nodes? Editting shouldn't matter; but not sure what happens if you are ADDING 2 nodes at the same time of the same type? Not sure it doesn't work; just been a long time since i worked on this. If this or other issues are real, and you can define a test case, please enter as a new issue.

found it, and the autosave appears to be happening, but I'm not getting new revisions. Any ideas? I'm using TinyMCE and revisions are turned on.

autosvae doesn't create revisions.. that would be pretty silly.. you would have 100's of revs in no time.

Revisions are edited/saved version of a document. Autosave is to prevent you from losing data if your browser dies. Not sure why you would think these would be related??

From the module page: "The autosave module automatically saves a node after a period of time using AJAX. All autosaved content are saved as revisions to ensure no content is overwritten."

Does it just create one revision then, and keep overwriting it? Either way, if I close my browser after an autosave, I can't get the content I was editing back.

i guess you must have one of the older versions of this module.. starting at rev 5.x-2.x it doesn't save nodes anymore - it only saves a snapshot of the form - the node is not saved and therefore no revision is created.

if you have the latest rev then you need to enable autosave for your node type. You should then see a popup at the bottom of your edit page when the autosave kicks in. If you kill your browser and then return to edit that node the popup should happen again telling you that there is a saved version of your node - you can then view the saved version, accept it as current or reject it.

pretty sure it does work; we use it on a site owned by the NY Times and it is used everyday by 100's of freelance writers.

The module also does work for me (using 5.x-3.1).

At first I didn't notice the popup at the bottom of the window, and before looking more closely at the module I was afraid it would create new revisions, so it might be a good idea to document the module's workings a little bit more in the readme file.

However, having such subtle and unobtrusive popups is a very good thing. We certainly don't want them to get in the way of the main task, which is editing the content.

I edited the Project page to more accurately explain what this (rev of the) module does.