CONTENT VISIBILITY FOR DIVI BUILDER
Content Visibility for Divi Builder compatibility with REEID Translate
Content Visibility for Divi Builder compatibility with REEID Translate is being evaluated from available plugin evidence. Conditional content display via PHP boolean expressions for Divi Sections and Modules (content shown/hidden based on expression evaluation). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Content Visibility for Divi Builder.
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
Content Visibility for Divi Builder is documented in the Security 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 Content Visibility for Divi Builder 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
- Conditional content display via PHP boolean expressions for Divi Sections and Modules (content shown/hidden based on expression evaluation).
- Expression validation that tokenizes expressions and enforces allowlists/denylists to prevent execution of potentially dangerous PHP code in visibility expressions.
- Configurable validation rules via developer filters, including: blocked function names, allowed PHP token types, allowed single-character tokens, and allowed callables (with a default allowlist including WordPress conditional tags).
- Safety behavior when validation blocks an expression: the plugin shows the content (rather than hiding it) and sends an email notification to the site admin with details about the blocked expression.
- Editor/publishing protection when validation is enabled: publishing is blocked at the editor for Divi 5/Gutenberg surfaces, and Divi 3 & 4 builders abort saving before database writes so existing content remains unchanged until corrected.
- Frontend behavior after deactivation/uninstall: the “Content Visibility” configuration option disappears from Divi Builder settings and has no effect on frontend output (while previously defined visibility settings persist in the database until the post/page is updated).
- Detection/instrumentation approach for Divi 4 and below vs Divi 5: modifies Sections/Modules by class inheritance (Divi 4 and below) or by instrumenting Gutenberg block render callbacks (Divi 5).
CONTENT BOUNDARY
Content Visibility for Divi Builder 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
Content Visibility for Divi Builder and REEID Translate FAQ.
What does Content Visibility for Divi Builder do according to the available plugin evidence?
Content Visibility for Divi Builder 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 Content Visibility for Divi Builder?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Content Visibility for Divi Builder?
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 Content Visibility for Divi Builder in a multilingual WordPress workflow.
REEID documents Content Visibility for Divi Builder 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.