Automatic saving of content

This is should be great!
I think that browser local storage can be useful too.

Autosave will need something like revision pinning.
So all partial autosaves write to the same revision. Otherwise wi will end up with a huge pile of revision, degrading database speed and eating up your storage.

That said, the workflow module adds something similar, but if we only have one single forward revision (per language), you can't see in revision who changed what / when inside a longer workflow process... Core is limiting us here.

IMHO we need much more advanced tools to manage the revision tree. Otherwise we will end up building crazy workaround systems...

I am the maintainer of autosave_form. It does not create revisions, but uses its own storage for the autosave_states. The reason is that it is basically impossible to save into revisions if there are defined DB constraints - such as NOT NULL. Additionally when talking about entity forms we don't only need the entity state, but also the form state. Also saving to a dedicated storage is faster than saving to entity tables and also does not make the revision tables to explode :).

I'll be happy to assist you if you have any questions or additional requirements.

Let's follow core

So we have a working PR and will merge it soon (https://github.com/thunder/thunder-distribution/pull/50)

Niiice!

I am on vacation until end of the week. Starting next week I am going to further support you on the issue queue of the module.

Well, this one was waiting a long time for completion :-) Thanks everyone!