=== Simple Revisions Delete === Contributors: briKou Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=7Z6YVM63739Y8 Tags: revisions, cleanup, delete, purge, gutenberg Requires at least: 6.4 Tested up to: 6.9 Requires PHP: 7.4 Stable tag: 2.0.2 License: GPLv2 or later License URI: http://www.gnu.org/licenses/gpl-2.0.html Delete the revisions of a post one by one or all at once, from the block editor, the classic editor or a bulk action. == Description == **Delete the revisions of your posts individually or all at once, either from the editor or through a bulk action. Works with both the block editor and the classic editor.** = What does it do? = Simple Revisions Delete adds a discreet purge control next to the revisions counter of the post you are editing. One click and the revisions of that post are gone. It helps you keep a clean database by removing unnecessary post revisions. Unlike most similar plugins, it lets you delete the revisions of a specific post rather than wiping every revision of your site at once. The plugin blends into the WordPress admin, relies exclusively on core functions to delete revisions safely, and adds no settings page: there is nothing to configure. = How does it work? = * In the **block editor**, a "Purge" button sits in the post status panel of the sidebar, right below the publishing options. It tells you how many revisions the post has and deletes them all in one request. * In the **classic editor**, the same control appears in the Publish metabox, and each revision listed in the Revisions metabox gets its own "Delete" button. * In the **posts and pages list**, a "Purge revisions" bulk action lets you clean up several posts at once. Everything happens in the background, so no page reload is needed: the block editor relies on the WordPress REST API, the classic editor on admin-ajax. Without JavaScript, the classic editor control falls back to a regular form submission and the bulk action keeps working. = What's new in 2.0? = The block editor integration has been rewritten from scratch. The previous version relied on jQuery and on the internal markup of the editor, which stopped working when Gutenberg 7.1 reorganised its DOM. The purge control is now a genuine editor plugin (`PluginPostStatusInfo`) reading and writing through a dedicated REST API, so it no longer depends on class names that can change at any release. The rest of the plugin has been rewritten too: one class per responsibility, no more inline `