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.

Adds a limit to the number of strings that can be imported in <a href="https://wordpress.org/plugins/glotpress/" rel="ugc">GlotPress</a>. 
It helps to prevent importing large translation projects, sets a reasonable limit to avoid performance issues. 
It allows to provide a free tier for users who needs it for small personal projects.
<h4>Configuration</h4>
Once you have installed GlotCore Limit Import Strings Number it is ready to use, and the initial limit is set to 1000 strings. 
You can change this limit by defining the following constant in your <code>wp-config.php</code> file: 
 <code>php 
define( 'GLOTCORE_IMPORT_STRINGS_LIMIT', 500 ); // Change 500 to your desired limit</code>

GlotCore Limit Import Strings Number

Adds a limit to the number of strings that can be imported in GlotPress.

GlotCore History Limiter vs GlotCore Limit Import Strings Number