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 reviewed using official plugin documentation. 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 text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Visibility Controls for Editor Blocks 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
Visibility Controls for Editor Blocks is documented in the Membership category with 6 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 Visibility Controls for Editor Blocks 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
- 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.
TRANSLATION BOUNDARY
Visibility Controls for Editor Blocks 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
Visibility Controls for Editor Blocks and REEID Translate FAQ.
What does Visibility Controls for Editor Blocks do?
Visibility Controls for Editor Blocks has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Visibility Controls for Editor Blocks 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 Visibility Controls for Editor Blocks?
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 Visibility Controls for Editor Blocks in a multilingual WordPress workflow.
REEID documents Visibility Controls for Editor Blocks 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.