
PERSISTENT LOGIN
Persistent Login compatibility with REEID Translate
Persistent Login compatibility with REEID Translate is being evaluated from available plugin evidence. Keeps users logged in by default when the Remember Me option remains checked, extending the login for up to one year and renewing that period on revisits. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Persistent Login.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Persistent Login is documented in the Security category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Persistent Login compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Keeps users logged in by default when the Remember Me option remains checked, extending the login for up to one year and renewing that period on revisits.
- Provides active-login controls that can limit how many devices or browsers a user may stay logged into at once.
- Can automatically end the oldest session or block a new login when an active-login limit is reached.
- Shows users their active sessions and login history in the WordPress admin profile area, including device and last-active information.
- Lets users end individual sessions from their profile page in wp-admin.
- Can notify users about logins from new devices and lets the site owner customize the notification email message.
- Includes an admin option to force-log out all users / end all sessions.
- Supports a premium mode with role-based persistent-login rules and configurable session duration, plus front-end session/history display via blocks and shortcodes.
CONTENT BOUNDARY
Persistent Login capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Persistent Login and REEID Translate FAQ.
What does Persistent Login do according to the available plugin evidence?
Persistent Login has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Persistent Login?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Persistent Login?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Persistent Login in a multilingual WordPress workflow.
REEID documents Persistent Login functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.