ROLE BASED CONTENT RESTRICTOR
Role Based Content Restrictor compatibility with REEID Translate
Role Based Content Restrictor compatibility with REEID Translate is being reviewed using official plugin documentation. Restrict access to posts, pages, and custom post types based on user roles or login status (logged-in vs logged-out/visitors). No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Role Based Content Restrictor does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Role Based Content Restrictor is documented in the Membership category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Role Based Content Restrictor compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
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.
TRANSLATION BOUNDARY
Role Based Content Restrictor capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Role Based Content Restrictor and REEID Translate FAQ.
What does Role Based Content Restrictor do?
Role Based Content Restrictor has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does Role Based Content Restrictor have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Role Based Content Restrictor?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Role Based Content Restrictor in a multilingual WordPress workflow.
REEID documents Role Based Content Restrictor functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.