meloniq

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


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.

Condless

<p>Limit the number of posts user can create. Any post type.</p>
<p><a href="https://en.condless.com/user-posts-limit/" rel="nofollow ugc">Documentation</a> | <a href="https://en.condless.com/contact/" rel="nofollow ugc">Contact</a></p>
<h4>How To Use</h4>
<ol>
<li>Plugin Settings: Select role, post type, limit, and cycle.</li>
</ol>
<h4>How It Works</h4>
<ul>
<li>On post creation the number of posts from this post type belong to this user for the specified cycle will be counted and if applicable the post creation will be prevented.</li>
</ul>
<h4>Features</h4>
<ul>
<li><strong>Post Creation Limits</strong>: Limit the number of posts each user role can create daily/weekly/monthly/yearly/ever.</li>
<li><strong>Hide Content</strong>: In order to make some content hidden when posts limit exceeded wrap it with the shortcodes (replace "post" with the post type of the relevant rules): [upl_hide type="post"][/upl_hide]</li>
<li><strong>Display Limits</strong>: Display the limits to the user anywhere with the [upl_limits] shortcode.</li>
<li><strong>Users Stats</strong>: Track how many posts each user used from his quota.</li>
<li><strong>Multisite</strong>: Network-wide rules can be applied via the Network Admin Dashboard (doesn’t support the Hide Content, Display Limits and Users Stats features).</li>
<li><strong>Integrations</strong>: WooCommerce, Paid Memberships Pro, MyListing theme, Restrict Content Pro, PeepSo, WordPress REST API.</li>
<li><strong>Limits per User</strong>: Set limits per user (see instructions in docs).</li>
</ul>


User Posts Limit

Отличный плагин

With a little elbow grease, the possibilities are really interesting for a multisite installation, such as limiting the total number of WooCommerce products per site (regardless of the author). The plugin is not easy to learn, not very intuitive and would surely deserve to be more explicit on certain settings, however, it does the job and the author is responsive and attentive… so I recommend it 👍 

Possibilities are really interesting for a multisite installation

Limit the number of posts user can create. Any post type.

GlotCore History Limiter vs User Posts Limit