|
|
|
|
|
|
by dz0ny
641 days ago
|
|
|
I would agree if revisions were enabled by default just for posts and pages. Here’s a common example: you have a blog with 20 pages and 20 custom plugins (quite a standard these days). In a year of hosting that one, you’ll end up with millions of revisions in the database, which is really resource and speed issue for MySQL servers as the developers of WordPress never considered sharding; everything is stuffed into one table, with no indexes by default. So, usually, the size of the DB and resources to run it go over what you would expect, so naturally, you limit it to a more sane value. TLDR; In pristine WP env with no plugins unlimited revisions make sense. In a WP with many plugins they don't as other plugins declare them but not use them and thus we end with a system that uses huge amount of resources for nothing. Oh and revision in WP is not like GIT revision as is full copy of the content. |
|
|
And if you could say "Keep revisions for 30 days" and/or "Keep the last 10 revisions for every post". Why that hasn't been implemented...