PRIVATE CONTENT LOGIN PROTECTOR
Private Content Login Protector compatibility with REEID Translate
Private Content Login Protector compatibility with REEID Translate is being evaluated from available plugin evidence. Gates front-end WordPress content behind a separate, custom login system that does not use or modify the normal WordPress login (wp-login.php) or the wp_users table No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Private Content Login Protector.
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
Private Content Login Protector 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 Private Content Login Protector 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
- Gates front-end WordPress content behind a separate, custom login system that does not use or modify the normal WordPress login (wp-login.php) or the wp_users table
- Provides fully custom login, forgot-password, and reset-password pages served at /private-login/
- Uses an independent user table (wp_pclp_users) with its own roles (Plugin Admin, Manager, Viewer) for access control to protected content
- Supports per-content protection via a “Protect this content” metabox for Pages, Posts, WooCommerce Products, and public Custom Post Types, plus bulk protection toggles (e.g., all products/categories/pages/posts/specific CPTs)
- Implements configurable session timeout and login attempt limits with lockout, along with password reset token expiry
- Maintains an activity log for login/logout/failed login/password reset events including IP and browser, and supports CSV import/export of users and JSON import/export of settings
- Offers front-end shortcodes for login/logout/current user state: [private_login], [private_logout], [current_private_user] (and prefixed aliases [pclp_login], [pclp_logout], [pclp_current_user])
- Provides a theme-able login screen with configurable visual elements (e.g., heading/sub-heading/logo/colors/border radius/font/card width)
CONTENT BOUNDARY
Private Content Login Protector 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
Private Content Login Protector and REEID Translate FAQ.
What does Private Content Login Protector do according to the available plugin evidence?
Private Content Login Protector 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 Private Content Login Protector?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Private Content Login Protector?
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 Private Content Login Protector in a multilingual WordPress workflow.
REEID documents Private Content Login Protector 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.