ROLE BASED CONTENT RESTRICTOR
Role Based Content Restrictor compatibility with REEID Translate
Role Based Content Restrictor compatibility with REEID Translate is being evaluated from available plugin evidence. Restrict access to posts, pages, and custom post types based on user roles or login status (logged-in vs logged-out/visitors). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Role Based Content Restrictor.
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
Role Based Content Restrictor is documented in the Membership category with 7 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 Role Based Content Restrictor 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
- Restrict access to posts, pages, and custom post types based on user roles or login status (logged-in vs logged-out/visitors).
- Provide per-content restriction configuration via a “Restrict Access” meta box, including selecting a restriction type and (when applicable) roles.
- Support a “Visitors Only” mode where logged-in users are redirected (with administrators always allowed access).
- Support a “Logged-in Users Only” mode to restrict content to authenticated users.
- Allow configuration of redirect targets: a custom redirect page per restricted content item and a global fallback redirect configured in plugin settings; if no redirect page is set, fallback behavior applies (and if no fallback is set, redirect to the homepage).
- Use a priority system to resolve restriction behavior when multiple restriction types were previously enabled (Visitors Only highest priority, then Logged-in Only, then role-based restriction).
- Provide backward-compatible handling of older saved configurations by mapping existing settings to the newer single “Restriction Type” selector UI without data loss.
CONTENT BOUNDARY
Role Based Content Restrictor 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
Role Based Content Restrictor and REEID Translate FAQ.
What does Role Based Content Restrictor do according to the available plugin evidence?
Role Based Content Restrictor has 7 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 Role Based Content Restrictor?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Role Based Content Restrictor?
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 Role Based Content Restrictor in a multilingual WordPress workflow.
REEID documents Role Based Content Restrictor 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.