The question really says it all. Here's the autosave docs page: http://imperavi.com/redactor/docs/settings/autosave/


I'm just thinking about what would need to happen in order for this to work.

  1. Craft would have to expose Redactor's autosave configuration somehow - either via UI or a Redactor config file.

  2. You'd have to write a plugin and point the autosave configuration to an action on a controller in your plugin.

  3. That action would be responsible for persisting the RTE content as well as the entry and field it came from (since you can have multiple RTEs on a page) - likely the database.

All-in-all, not a very robust solution. It'd be much more likely that we implemented our own autosave solution that worked for all fields at the entry level, instead of just the RTE.

  • 1
    Autosave feature – sounds like a worthy feature request! Sep 29 '15 at 23:07
  • Ahh, indeed, an all-fields autosave feature would indeed be awesome! Especially since Redactor kinda stinks and hopefully will be replaced with something saner and more mature, like TinyMCE or CK Editor...
    – Sandwich
    Sep 30 '15 at 1:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.