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

Norskes wrote a good sample of what could be. You comments are welcome. Check out https://github.com/ClassicPress/ClassicPress/pull/436

See also: https://forums.classicpress.net/t/petition-setting-for-the-number-of-revisions-stored-in-the-database/1333

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.

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).

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