CLASSIC EDITOR AND CLASSIC WIDGETS
Classic Editor and Classic Widgets compatibility with REEID Translate
Classic Editor and Classic Widgets compatibility with REEID Translate is being evaluated from available plugin evidence. Disables the Gutenberg/block editor and enables the Classic Editor experience. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Classic Editor and Classic Widgets.
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
Classic Editor and Classic Widgets is documented in the Other category with 8 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 Classic Editor and Classic Widgets 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 Gutenberg/block editor and enables the Classic Editor experience.
- Provides Classic Widgets support for the Widgets screen and the Customizer widgets screen.
- Can disable Gutenberg globally or for specific post types.
- Includes an editor switcher so editors can be changed per post.
- Can set a default editor and a widgets editor.
- Supports hiding the plugin menu item.
- Can enable or disable frontend Gutenberg styles.
- Lists compatibility support for Advanced Custom Fields, WooCommerce, WPML, and Polylang.
CONTENT BOUNDARY
Classic Editor and Classic Widgets 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
Classic Editor and Classic Widgets and REEID Translate FAQ.
What does Classic Editor and Classic Widgets do according to the available plugin evidence?
Classic Editor and Classic Widgets has 8 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 Classic Editor and Classic Widgets?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Classic Editor and Classic Widgets?
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 Classic Editor and Classic Widgets in a multilingual WordPress workflow.
REEID documents Classic Editor and Classic Widgets 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.