This project is not covered by Drupal’s security advisory policy.
Synopsis
Autosave node performs autosaves to a journaling table in case something happens to the network connection that makes it impossible for the user to save later. We are using this on some of our projects where the strict webserver security configurations sometimes conflict with and block the content that users put into the node bodies, even though that content may not, in of itself, pose a security threat. Some of our users are not technical and do not understand the best practise of saving often. In such a case, at least what was written so far by the user is saved for possible restoration.
We are using this actively, but since this concerns content, please use this at your own risk. We bear no responsibility for any data lost as a result of use of this module. However, we are mitigating such risk by journaling to a separate table, rather than touching the core node content.
Known problems
We hope that the "security advisory" will go away after first audit of the module.
Similar projects
We needed a module for Drupal 7, and these were the only that we found:
- Node autosave: sandbox project, where the last update was a number of years ago.
- Autosave: No further development, and we ran into questions in the Internet about stability.
- CKEditor autosave: Drupal 8, and seeking new owners.
Restrictions
Journaling is made to a separate table for safety purposes. However, this means that the user needs to visit the autosave dashboard page to restore any lost content.
Project information
- Project categories: Content editing experience
- Created by jentre on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
