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.

Joel James

Duck Dev

Loggedin is a lightweight WordPress plugin that lets you easily limit the number of simultaneous active sessions a user can have. This is a crucial feature for membership sites, online courses, and other platforms where you need to prevent users from sharing their accounts.
<h3>🎁 Features</h3>
<ul>
<li>Set Global Limits: Define a maximum number of concurrent logins for all users.</li>
<li>Flexible Login Behavior: Choose to either block new logins when the limit is reached or automatically log out the oldest session to allow a new one.</li>
<li>Prevent Account Sharing: By limiting sessions, you can effectively stop users from sharing their login credentials with others.</li>
<li>Admin Control: Easily force log out a user from the admin dashboard, giving you full control over active sessions.</li>
<li>Developer-Friendly: The plugin is built with a hook-based architecture, making it highly customizable and extensible for developers.</li>
</ul>
<h3>📦 Addons</h3>
Enhance LoggedIn’s functionality with these simple yet powerful <a href="https://duckdev.com/addons/loggedin/" rel="nofollow ugc">add-ons</a>.
<ul>
<li>
<a href="https://duckdev.com/addon/limit-per-user/" rel="nofollow ugc">Limit Per User</a>: For more granular control, the Limit Per User addon allows you to set specific login limits for individual users, overriding the global settings. This is perfect for offering different tiers of access or special privileges.
</li>
<li>
<a href="https://duckdev.com/addon/limit-per-role/" rel="nofollow ugc">Limit Per Role</a>: For flexible, group-based control, the Limit Per Role addon allows you to set specific login limits for individual roles, overriding the global settings. This is perfect for managing access across different user groups or membership tiers.
</li>
<li>
<a href="https://duckdev.com/addon/real-time-logout/" rel="nofollow ugc">Real-time Logout</a>: This add-on ensures a truly seamless experience by checking for logouts in real time. When a user’s session is terminated in the background due to a login limit, the add-on will automatically refresh their page, instantly restricting access.
</li>
</ul>
<h3>🐛 Bug Reports</h3>
Found a bug? We welcome your bug reports! Please report any issues directly on the <a href="https://github.com/Joel-James/loggedin/issues" rel="nofollow ugc">Loggedin GitHub repository</a>.
Please note: GitHub is for bug reports and development-related issues only. For support, please use the WordPress.org support forums.

Loggedin – Limit Concurrent Sessions

Good Plugin

Good

Lightweight plugin that limits an account to a specific number of concurrent logins.

GlotCore History Limiter vs Loggedin – Limit Concurrent Sessions