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 reviewed using official plugin documentation. Disables the block editor and restores the Classic Editor across the site by default. No specific text shown to visitors is currently confirmed for translation.
Visit No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor ↗
AWAITING VERIFICATION
What No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor 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
No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor is documented in the Other category with 7 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 No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor 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
- 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.
TRANSLATION BOUNDARY
No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor 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 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.
FREQUENTLY ASKED 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?
No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor 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 No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor?
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 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 confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.