NO GUTENBERG?
No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor compatibility with REEID Translate
No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor compatibility with REEID Translate is being evaluated from available plugin evidence. Disables the block editor and restores the Classic Editor across the site by default. No specific visitor-facing translation surface is currently confirmed.
Visit No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor ↗
AWAITING VERIFICATION
What the available evidence establishes for No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor.
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
No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor is documented in the Other 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 No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor 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
- Disables the block editor and restores the Classic Editor across the site by default.
- Can narrow block-editor disabling by post type, user role, page template, or individual entry.
- Supports per-entry editor switching between Classic and Blocks for selected post types.
- Removes block-related site features such as Global Styles, block widgets, block patterns, theme.json processing, and the Site Editor.
- Removes block CSS and JavaScript assets from the frontend and related admin contexts when the Classic Editor is used.
- Includes WooCommerce-specific behavior for the block-based product editor and WooCommerce block assets.
- Can be configured from wp-config.php, including locking or hiding the settings screen and applying settings across multisite networks.
Distinctive features
Site-wide Classic Editor restoration with granular control by post type, role, template, or individual entry. Includes block-feature removal beyond the editor itself, plus WooCommerce-specific handling and wp-config.php-based configuration options.
CONTENT BOUNDARY
No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor 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 plugin changes editor availability and block-related site features, but the available evidence does not establish broader compatibility beyond those documented behaviors. Per-entry editor switching is described only for selected post types. WooCommerce-specific behavior is documented for the block-based product editor and WooCommerce block assets. Evidence for translation-surface behavior is not established.
COMMON QUESTIONS
No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor and REEID Translate FAQ.
What does No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor do according to the available plugin evidence?
No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor 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 No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor?
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 No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor in a multilingual WordPress workflow.
REEID documents No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor 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.