
DIVI CONTENT RESTRICTOR
Divi Content Restrictor compatibility with REEID Translate
Divi Content Restrictor compatibility with REEID Translate is being evaluated from available plugin evidence. Conditionally restrict partial content on Divi page elements (specifically Divi sections). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Divi 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
Divi Content Restrictor is documented in the Membership category with 6 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 Divi 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
- Conditionally restrict partial content on Divi page elements (specifically Divi sections).
- Provides Divi Visual Builder compatibility for the restriction behavior on Divi section modules.
- Supports access conditions based on logged-in status and user roles (including “any/all selected roles”).
- Includes an “Un-Authorized Text” setting to display an unauthorized message and apply text styles when access is not granted.
- Implements restriction condition toggles on the Divi section module’s Advanced tab, including a “Restrict Content” toggle and an “Un-Authorized Text” toggle.
- Supports integration-based restriction conditions with third-party membership/access plugins: WooCommerce Membership, MemberPress, Restrict Content Pro, and “Custom WordPress Filter” (as described in the plugin text).
CONTENT BOUNDARY
Divi 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
Divi Content Restrictor and REEID Translate FAQ.
What does Divi Content Restrictor do according to the available plugin evidence?
Divi Content Restrictor has 6 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 Divi 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 Divi 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 Divi Content Restrictor in a multilingual WordPress workflow.
REEID documents Divi 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.