VISIBILITY CONTROLS FOR EDITOR BLOCKS
Visibility Controls for Editor Blocks compatibility with REEID Translate
Visibility Controls for Editor Blocks compatibility with REEID Translate is being evaluated from available plugin evidence. Adds native visibility settings in the WordPress block editor sidebar for Gutenberg blocks, allowing blocks to be hidden or shown based on device type (mobile/tablet/desktop). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Visibility Controls for Editor Blocks.
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
Visibility Controls for Editor Blocks 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 Visibility Controls for Editor Blocks 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
- Adds native visibility settings in the WordPress block editor sidebar for Gutenberg blocks, allowing blocks to be hidden or shown based on device type (mobile/tablet/desktop).
- Provides login-status-based visibility controls so blocks can be shown/hidden for logged-in users versus non-logged-in visitors (guests).
- Supports custom breakpoints to define what counts as mobile and tablet for the site/theme.
- Synchronizes device visibility controls with WordPress’s built-in “Hide block” modal on WordPress 7.0+ so changes in either place update the same block visibility setting.
- Works with dynamic Gutenberg blocks and block theme/site editor rendering contexts (server-rendered/dynamic blocks).
- Pro version (separate add-on) extends membership-related visibility with user role visibility, plus date/time scheduling and URL/query parameter rules; role-based rules are stated to remain server-side for privacy.
CONTENT BOUNDARY
Visibility Controls for Editor Blocks 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
Visibility Controls for Editor Blocks and REEID Translate FAQ.
What does Visibility Controls for Editor Blocks do according to the available plugin evidence?
Visibility Controls for Editor Blocks 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 Visibility Controls for Editor Blocks?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Visibility Controls for Editor Blocks?
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 Visibility Controls for Editor Blocks in a multilingual WordPress workflow.
REEID documents Visibility Controls for Editor Blocks 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.