Michael Sablone

Optimize your website’s performance and streamline your editing workflow with the Time-based Revision Cleanup plugin for WordPress. Our plugin offers a sophisticated solution to the limitations of the default number-based revision system, which can quickly become inadequate for active sites. Instead of restricting revisions to a set count, our plugin allows you to specify a timeframe for keeping revisions, such as 30, 60, or 365 days, ensuring that your database retains only what’s necessary without losing the essential edit history of your posts.
In addition, our plugin enhances the admin dashboard with an analytics feature to generate visual representations of revision history data.
<h3>Key Features:</h3>
<ul>
<li>Intelligent Age-Based Management: Preserve your site’s history by automatically deleting revisions past a certain age, keeping only the recent and relevant changes.</li>
<li>Seamless On-Save Cleanup: The plugin intuitively removes outdated revisions upon saving posts, based on the age criteria you’ve set, without disrupting the creative process.</li>
<li>Optional Automated Cleanup: Enable the optional CRON job to perform regular, site-wide revision cleanups at intervals you control, maintaining optimal database health with no manual effort.</li>
<li>Dashboard Analytics: Visualize your site’s revision cleanup activity with an integrated chart, powered by Google’s Chart API.</li>
<li>Fully Customizable: Configure the plugin’s settings to fit the unique demands of your site, including save timeout, CRON frequency, and the maximum number of revisions to process.</li>
</ul>
By focusing on time rather than revision count, our plugin addresses the core flaw in the default system, ensuring that a busy day of editing won’t result in the loss of important historical data. With the optional CRON job for hands-free maintenance, adjustable settings for precision control, and insightful analytics, the Time-based Revision Cleanup plugin is an essential tool for maintaining a healthy, efficient WordPress site.

Time-based Revision Cleanup


I installed the Time-Based Revision Cleanup plugin on my site and and it really is a nifty plugin. You can tell the developer knows what he's doing. Really love the chart visualization and the fact that it does the work of keeping my db clean and up-to-date. Thanks for the cool plugin!


Well-designed with the user in mind

Maximize WordPress efficiency with Time-based Revision Cleanup: manage post histories by age, not count, with optional auto-cleanups.

meloniq

Controls and optimizes translation history in <a href="https://wordpress.org/plugins/glotpress/" rel="ugc">GlotPress</a> by enforcing limits on <code>waiting</code> and <code>old</code> entries per string, 
reducing unnecessary revisions and keeping the database lean and efficient.
<ol>
<li>
It limits the number of <code>waiting</code> translations. 
Any <code>waiting</code> translations above the limit are set to <code>old</code> status and are no longer shown in the waiting translations list.
</li>
<li>
It limits the number of <code>old</code> translations. 
Any <code>old</code> translations above the limit are permanently deleted from the database.
</li>
</ol>
<h3>How the limit works</h3>
Assume the limit is set to 2 translations per string.
<h3>1. Single user behavior</h3>
When a single user submits multiple translations:
<ul>
<li>The latest translation is always marked as <code>waiting</code></li>
<li>The previous <code>waiting</code> translation becomes <code>old</code></li>
<li>If the number of <code>old</code> translations exceeds the limit:
<ul>
<li>The oldest <code>old</code> translation is deleted</li>
</ul>
</li>
</ul>
Result: 
– <code>1 waiting</code> translation (latest) 
– Up to <code>2 old</code> translations (limited)
<h3>2. Multiple users</h3>
When multiple users submit translations for the same string:
<ul>
<li>Each user can have one <code>waiting</code> translation</li>
<li>
A new submission:
<ul>
<li>Replaces that user’s previous <code>waiting</code> (which becomes <code>old</code>)</li>
<li>Does affect other users <code>waiting</code> translations if the total number of <code>waiting</code> translations exceeds the limit</li>
<li>The oldest <code>waiting</code> translation over the limit (regardless of user) becomes <code>old</code></li>
</ul>
</li>
<li>
All <code>old</code> translations are shared (counted globally per string)
</li>
<li>All <code>waiting</code> translations are shared (counted globally per string)</li>
</ul>
<h4>Configuration</h4>
Once installed, GlotCore History Limiter is ready to use. The default limit is set to 3 history entries per string.
You can change this limit by defining the following constant in your <code>wp-config.php</code> file: 
 <code>php 
define( 'GLOTCORE_HISTORY_LIMIT', 3 ); // Change 3 to your desired limit</code>
You can also modify the limit by hooking into the <code>glotcore_history_limit</code> filter in your theme or plugin: 
 <code>php 
add_filter( 'glotcore_history_limit', function( $limit ) { 
 return 3; // Change 3 to your desired limit 
} );</code>

GlotCore History Limiter

Limits and manages translation history in GlotPress by controlling the number of waiting and old entries per string to prevent database bloat.

Time-based Revision Cleanup vs GlotCore History Limiter