ClassicPress PetitionsClassicPress Petitions
This is a read-only archive. Post or comment on the live version of this page on our forums.

Add a setting to limit the number of revisions stored in the database

July 2, 2019 · 22:41 · Alan Coggins

All revisions to posts and pages are saved by default. This can lead to unnecessary bloat in the database over time. I suggest adding a simple number box on the Settings -> Writing page to allow users to set the number of revisions saved (with zero indicating no revisions are to be kept).

+14 more
Laurence Bahiirwa

Norskes wrote a good sample of what could be. You comments are welcome. Check out

Tim Kaye

There is already a constant that can be put in wp-config.php that achieves this. (I typically use it to allow no revisions to be stored whatsoever.) But I can see this might be worth exposing as a setting within the admin pages. However, the discussion on the forums seems to have turned to making this a per-post setting. That, it seems to me, would very definitely be plugin territory.


It's a no from me on this -- esp. per-post, which is kinda ridiculous.

One of the things that WordPress has always understood (mostly) is the difference between newbie users and advanced developers.

The vast majority of typical users wouldn't understand this setting, and might even end up causing themselves problems by configuring it "wrong". So in the spirit of WordPress usability, I think its better to keep advanced settings hidden from the UI and allow developers or web hosts to configure those in the background.

ClassicPress should avoid being too aggressive in reducing database bloat at the cost of data loss or user confusion. Remember that most of the people offering feedback here are skilled developers, and things are much, much different from the perspective of typical users.

James Nylen

As originally discussed on another petition, I think this should stay as-is (if you need this advanced feature and you are comfortable with the implications around data loss, then you can edit wp-config.php to put it in place).

Laurence Bahiirwa

Does this warranty a “won’t-fix” close?