{"id":38112,"date":"2015-08-10T00:34:09","date_gmt":"2015-08-10T00:34:09","guid":{"rendered":"https:\/\/wordpress.org\/plugins-wp\/revision-strike\/"},"modified":"2017-09-16T17:45:53","modified_gmt":"2017-09-16T17:45:53","slug":"revision-strike","status":"publish","type":"plugin","link":"https:\/\/bs.wordpress.org\/plugins\/revision-strike\/","author":7129452,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_crdt_document":"","version":"0.6.0","stable_tag":"0.6.0","tested":"4.8.28","requires":"4.2","requires_php":"5.4","requires_plugins":"","header_name":"Revision Strike","header_author":"Steve Grunwell","header_description":"","assets_banners_color":"","last_updated":"2017-09-16 17:45:53","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/stevegrunwell.com\/blog\/revision-strike","header_author_uri":"https:\/\/stevegrunwell.com","rating":5,"author_block_rating":0,"active_installs":70,"downloads":5878,"num_ratings":1,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":[],"upgrade_notice":{"0.6.0":"

Fixed bug where warnings were being thrown when Revision Strike was being run verbosely via WP-CLI.<\/p>","0.3.0":"

Added new revisionstrike_get_revision_ids<\/code> filter.<\/p>","0.2":"

Performance enhancements, added a strike-all<\/code> WP-CLI command to automatically clean up all<\/em> of your eligible post revisions in one fell swoop.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":"1"},"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1","0.2","0.3.0","0.4.0","0.4.1","0.5.0","0.6.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":"1216698","resolution":"1","location":"assets"}},"screenshots":{"1":"The Tools > Revision Strike page in action."},"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[4567,732,247,6243],"plugin_category":[52,54,59],"plugin_contributors":[81424],"plugin_business_model":[],"class_list":["post-38112","plugin","type-plugin","status-publish","hentry","plugin_tags-cron","plugin_tags-maintenance","plugin_tags-performance","plugin_tags-revisions","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_category-utilities-and-tools","plugin_contributors-stevegrunwell","plugin_committers-stevegrunwell"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/revision-strike.svg","icon_2x":false,"generated":true},"screenshots":[{"src":"https:\/\/ps.w.org\/revision-strike\/assets\/screenshot-1.png?rev=1216698","caption":"The Tools > Revision Strike page in action."}],"raw_content":"\n

Unless post revisions are explicitly limited, WordPress will build up a hefty sum of revisions over time. While it's great to have revision history for some recent content, the chances that old revisions will be necessary diminish the longer a post has been published. Revision Strike is designed to automatically remove these unneeded revisions on older, published posts.<\/p>\n\n

How does it work?<\/h4>\n\n

First, a threshold is set, with a default of 30 days. Once a day, Revision Strike will run and find any post revisions in the database attached to published posts with a post date of at least 30 (or your custom threshold) days ago, and \"strike\" (tear-down and remove) them from the WordPress database.<\/p>\n\n

Contributing<\/h4>\n\n

If you'd like to help build Revision Strike, please visit the plugin's GitHub page<\/a>. Contributors are welcome, and details can be found in the repo's README file<\/a>.<\/p>\n\n\n

    \n
  1. Upload the revision-strike\/ directory to your WordPress installation's plugin directory (by default, \/wp-content\/plugins).<\/li>\n
  2. Activate the plugin through the 'Plugins' menu in WordPress.<\/li>\n<\/ol>\n\n

    Activating the plugin will automatically register a daily WP Cron event to clean up revisions on established posts. If you'd prefer not to wait, you can explicitly purge post revisions through the 'Tools > Revision Strike' page within WordPress or with WP-CLI<\/a>.<\/p>\n\n\n

    \n
    Installation Instructions<\/dt>\n
      \n
    1. Upload the revision-strike\/ directory to your WordPress installation's plugin directory (by default, \/wp-content\/plugins).<\/li>\n
    2. Activate the plugin through the 'Plugins' menu in WordPress.<\/li>\n<\/ol>\n\n

      Activating the plugin will automatically register a daily WP Cron event to clean up revisions on established posts. If you'd prefer not to wait, you can explicitly purge post revisions through the 'Tools > Revision Strike' page within WordPress or with WP-CLI<\/a>.<\/p><\/dd>\n

      Can I configure how long a post needs to be published before its revisions can be removed?<\/dt>\n

      Yes. On the Settings > Writing page there is an option to set the default number of days a post must be published before removing its revisions, but out of the box it's 30 days.<\/p><\/dd>\n

      Can I manually run Revision Strike without having to wait for the daily WP Cron event?<\/dt>\n

      Yup, just visit Tools > Revision Strike within the WordPress admin area. If you're a WP-CLI<\/a> user, you can also run Revision Strike from the command line (run wp revision-strike clean --help<\/code> for a full list of options).<\/p><\/dd>\n\n<\/dl>\n\n\n

      For a full list of changes, please see the Change Log in the GitHub repo<\/a>.<\/p>\n\n

      0.6.0<\/h4>\n\n

      September 16, 2017<\/em><\/p>\n\n