Modernize for Drupal 7

Just wanted to say that my wife thanks you. I build the sites, and without features like this, I get in trouble. So THANKS!

Any chance of seeing the work in progress in a sandbox?

We are about to use this module for a D6 project and would be happy to backport the improvements you've made. Especially with the JS layer.

We have a very short sprint window for this and would look to release our updated code mid next week.

Hello guys,

Some time ago i need this feature for one of my projects, but just porting autosave module to Drupal 7 wouldn't suite my needs, so that I've created my own module and willing to share it with you. At first i wanted to create a new project for it, called "node_autosave", as it's completely different module and no code was taken from autosave. But i think for other people interested in this functionality and users who already use autosave will be much easier if it will be one module. So if module maintainers agree to merge modules, i would be happy to commit it like 2.x branch

Feel free to test it http://drupal.org/sandbox/dzhgenti/1316894 and let me know what do you think of this.

Thanks,
Dmitry

hey Guys.

So i've been trying to backport dzhgenti's work to 6 and looking at his approach. I like several things about it (several storage engines etc). However, both modules are for traditional node forms only, one of our requirements is saving of non generic forms (for integration with multi_node_edit), we also have dreams of processing saved node forms after the fact.

I'm loathed to do this, but due to my time constraints i'm about to kill some kitties (not hacking core) but by re-writing this module yet again to support generic forms and be slightly less reliant on JS (quicksave now button).

Will likely publish in a sandbox in case its of interest.

@Crell: Sweet, looks like my timing for looking for this kind of feature is good.

I'm looking to use it together with the Workbench suite of modules, and particularly the the combination with Workbench Moderation is interesting where work can be done on new revisions while an older is still live and published. The Media module is another one for adding and maintaining media to the content.

The D5/6 versions seems to have been pretty much only for nodes. In D7 we got entities and fields can be added on many other things as well. Is the plan to add support for autosaving on field level as well so it works for taxonomy, users, files and so on?

@crell: Nice, have a private project I'm working on that I will test this out for. A bit busy next couple of days, but hopefully I can give a report back during the coming week.

Thanks for taking this on, going to be a great feature to assure as little as possible is lost when browser/computer crashes.

looks cool. looks as though same general concept as we had before; which i think was the right approach in general. for some reason i thought you were suggesting using revisions to store backups which i couldn't see how that could work.

one thing that you seem to have dropped or maybe missed or haven't gotten to is that when you edit a node which has a saved version; in the D6 module you were able to toggle back and forth between the saved and autosaved - which i think is necessary to be able to decide which version is the best to keep. the way the module is now you seem to only get one crack at it - once you have selected "restore" there is no changing your mind (although could simply hit Edit again).

also, once hitting restore; there is an odd popup that lets you again choose ignore/restore.. but it quickly goes away and does not come back.

i guess with an actual release now (even as -dev) should likely close this thread and start to post separate issues - likely much easier to track that way.

if i get to more testing; i'll raise separately .

thanks for getting this back on track... really is an important module.

hmm.. ok.. lots of issues still - perhaps too soon to start testing unless you want me to start raising issues then i could; but not really functional at the moment i don't think.

yea, was curious to see what revisions idea was going to be.. :)

maybe flipback isn't needed but i don't quite get how it isn't; i'll have to play around a bit more... i don't think i can look at what was saved and then decide that isnt what i wanted - that seems pretty basic.

so quick list, but i'll raise sep tickets:

- once i pick any of the options.. autosave no longer saves anything
- doesnt work with wysiwyg; which was tricky in earlier version and i think you suggested shouldn't matter; but possibly that was when you were still thinking revs
- when you pick ignore; i think you should flush entry from table (since you have just stated you don't want that saved version) - but maybe less confusing if autosave kicks in again as it will soon wipe that entry with a new one

I'll add one more issue to @liquidcms' list.

- For those not using TinyMCE, the tinymce check in autosave.js breaks everything. Perhaps this is the same as liquidcms' second point about wysiwug compatibility.

I'm using CKeditor and hope that the "generic" wysiwug compatibility can be accomplished easily.

i am using Tiny. But it does seem to work now; will need to test more.

although, on restore, it does wipe out css in the text area:

initial edit: http://screencast.com/t/u2TaytFJV
after restore: http://screencast.com/t/xTgutsJS

and as before, from that last screen shot; not sure which option to pick to keep my lost changes? do i pick Restore again? and if i don't pick fast, i lose the popup and then AS never triggers again.

The second, I only tested it with tinymce, as almost never use CKEditor. But it does work with Tiny. (Using the server-side form rebuild simplified a lot.) The only catch is that you have to manually sync the textarea and the wysiwyg. That was working for me, however.

Have you tested with a basic form that doesn't have an RTE (TinyMCE, CKeditor) enabled? I disabled WYSIWUG altogether and get a JavaScript error complaining that tinymce isn't defined.

Also, are their module settings or permissions to be set? I don't see either. If so, that's great. I'm all for simplicity.

I'd suggest a more formal check.

if (typeof tinymce !=== 'undefined') {
...
}

It definitely eliminates the error if TinyMCE is disabled, but then autosave isn't working at all. If you disable WYSIWUG and TinyMCE altogether, is autosave activating on edit forms for you?

I am seeing the same as #22 - if I don't have TinyMCE, then nothing at all seems to autosave. I will try to investigate further when I get the chance.