ENABLE BLOCK EDITOR FOR WC PRODUCTS
Enable Block Editor for WC Products compatibility with REEID Translate
Enable Block Editor for WC Products compatibility with REEID Translate is being reviewed using official plugin documentation. Enables the WordPress block editor (Gutenberg) for WooCommerce product edit screens. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Enable Block Editor for WC Products 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
Enable Block Editor for WC Products is documented in the Other 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 Enable Block Editor for WC Products 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
- Enables the WordPress block editor (Gutenberg) for WooCommerce product edit screens.
- Provides an extensible “saver framework” (savers registry) to persist third-party data on “Update” when Gutenberg save-cycle behavior would otherwise cause data loss.
- Includes a bundled WooCommerce variations saver adapter that preserves variation edits on “Update” by re-triggering WooCommerce’s native variation save action (via clicking WooCommerce’s variation save button when variation rows are dirty).
- Integrates with the Gutenberg save cycle by subscribing to the data store and running registered savers on the saving→saved transition (autosaves ignored).
- Supports a “classic” fallback strategy for variable products via `EBEFWCP_MODE` (or `ebefwcp_mode` filter), where the bridge is not loaded for that mode.
- Provides a developer-facing public API on `window.ebefwcp.registerSaver(…)` to register custom savers using selectors for “dirty” rows and the button that triggers the native save.
TRANSLATION BOUNDARY
Enable Block Editor for WC Products 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
Enable Block Editor for WC Products and REEID Translate FAQ.
What does Enable Block Editor for WC Products do?
Enable Block Editor for WC Products has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Enable Block Editor for WC Products 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 Enable Block Editor for WC Products?
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 Enable Block Editor for WC Products in a multilingual WordPress workflow.
REEID documents Enable Block Editor for WC Products 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.