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

<ol>
<li><p>Craft would have to expose Redactor's autosave configuration somehow - either via UI or a Redactor config file.</p></li>
<li><p>You'd have to write a plugin and point the <a href="http://imperavi.com/redactor/docs/settings/autosave/#setting-autosave" rel="nofollow">autosave configuration</a> to an action on a controller in your plugin.</p></li>
<li><p>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.</p></li>
</ol>

<p>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.</p>

CC BY-SA 3.0
2015-09-29T23:07:38.900Z
Autosave feature – sounds like a worthy [feature request](http://feedback.buildwithcraft.com/)!
Mats Mikkel Rummelhoff
CC BY-SA 3.0
2015-09-30T01:10:21.170Z
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
CC BY-SA 3.0
2015-09-29T17:52:15.070Z
2015-09-29T17:52:15.070Z
Brad Bell
<p>The question really says it all. Here's the autosave docs page: <a href="http://imperavi.com/redactor/docs/settings/autosave/" rel="nofollow">http://imperavi.com/redactor/docs/settings/autosave/</a></p>

<richtext><json>
Can Craft's Rich Text fields be configured to use Redactor's autosave?
# Can Craft's Rich Text fields be configured to use Redactor's autosave?

(Asked by: username_0 on 2015-09-29)

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

**Tags:** richtext, json

---

## 1 answers

### Answer by username_1 on 2015-09-29. Score: 1 | Accepted answer

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](http://imperavi.com/redactor/docs/settings/autosave/#setting-autosave) 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.

> **Comments:**
> **username_2**: Autosave feature – sounds like a worthy [feature request](http://feedback.buildwithcraft.com/)!  
> **username_0**: 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...  

---

