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.

Bruno Cantuaria

Most users like to upload their fresh shotted pictures to WordPress directly from their digital camera, and what happens? Full disk, reach bandwith limit and slowdown the site with heavy images.
Limit Image Size is a smart plugin wich will limit the megapixel an image can have. When you upload an image, plugin will check if it have more megapixels than you limited, if so, the plugin will automatically resize the image to have that megapixel. This will save space in disk, site’s bandwith and will make your site faster.
Limit Image Size works with 3 methods to resize, not all of them will be enabled on your site but the plugin will choose the best one available for you. The 3 methods are:
<ul>
<li>ImageMagick – The best method with the best performance, but requires that your host have installed the ImageMagick extension on your server.</li>
<li>WebService – This method sends a copy of your image to a webservice which will resize it and sends it back to your site. It’s not the fastest way but is a good one for limited sites.</li>
<li>GD – This method is native to PHP but demands a lot of processing from your server. The plugin will use it only if no other method is available.</li>
</ul>
So, there is no cons to Limit Image Size. Just install it and you will never more need to care about the size of your pictures.

Limit Image Size

Limit Image Size will save space in disk and bandwith resizing large images when you upload them to WordPress.

GlotCore History Limiter vs Limit Image Size