Closed (won't fix)
Project:
Autosave
Version:
5.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
28 Feb 2007 at 22:12 UTC
Updated:
7 Jul 2013 at 02:04 UTC
After a while, and depending on the frequency of the autosaves, the database will be full of autosave revisions!
Is there a way to categorize the autosave revisions and to delete them after maybe :
- the node edition/creation is done
- or on daily/weekly basis
This clean up frequence could be a setting of the module.
Comments
Comment #1
edmund.kwok commentedHmm, in the development snapshot version, there is only one autosaved revision for each adding/editing session. Please refer to http://drupal.org/node/133078. There should be significantly less revisions compared to the previous version.
But what do you suggest?
1. Autosaved revisions are deleted after the node is submitted
2. Cron to remove autosaved revisions are x number of days/hours/revisions
3. A configurable maximum autosaved revision per node
Or all three? I would rely on your feedback as I don't use autosave very much myself :p
Comment #2
scor commentedI don't like the third one. I think the first solution would fix the problem.
We need more feedback from other users here.
Comment #3
Crashtest commentedI like the first and second solution. The first would be sufficient in my eyes. But the second could also be very practical.
Comment #4
edmund.kwok commentedI think 1 and 2 could solve the problem. Like scor said, we need input and opinions from other users.
Bear in mind with the discussions happening in http://drupal.org/node/156036, we might need to consider this issue as well when autosaved works with all other forms.
Comment #5
Crell commented