What problem is your feature request going to solve? Please describe.
Recently I had a problem with my page never saving. I always got '500' server errors every time I pressed 'UPDATE'. The size of the page being saved was the issue. My server memory limit was being hit. My page was not long and the content normal. However I accumulated at least 100 revision states over many days. After manually deleting 20-or-so older revision states, one by one, the '500' errors never occurred.
Basically getting rid of revision states made my page smaller, so it never hit my server memory limit when attempt saving. This concept was never communicated to me, and I discovered it by accident.
Describe the solution you'd like
At the top of History / Revisions, there should be some kind of control that allows one to delete all revision states older than X. Currently you can only delete revision states manually, one-by-one, with multiple clicks, by pressing 'X' on each, and going through a prompt.
Instead there should be one link at the top that allows you to bulk delete revisions based on conditions. For example, "Delete revisions older than 2 days". Or the deletion could be by number... like "Delete all revision states except for the last 30 items".
Going further, there should be a global revisions control... "Delete ALL revisions". This should clear up a ton of space in a database.
In any case, this whole concept of revision management could be better communicated to the user. I only came upon it by accident, even after research.
@TheMangoTrain
Elementor uses the native WP revisions system, which means you can either disable it or limit its to your needs:
define( 'WP_POST_REVISIONS', false );
define( 'WP_POST_REVISIONS', 3 )
Other than that, you delete revisions either via a 3rd party plugin or a simple sql query:
DELETE FROM wp_posts WHERE post_type = "revision";
thanks.
Thanks, I can do those things... but for non-techie users, they'd need better UI (a shortcut) or better UX (a message that indicates what to do), especially if the idea is for Elementor to be a better product, which is ultimately the point of the feature request.
+1
Most helpful comment
Thanks, I can do those things... but for non-techie users, they'd need better UI (a shortcut) or better UX (a message that indicates what to do), especially if the idea is for Elementor to be a better product, which is ultimately the point of the feature request.