CUSTOM FIELDS FOR GUTENBERG
Custom Fields for Gutenberg compatibility with REEID Translate
Custom Fields for Gutenberg compatibility with REEID Translate is being reviewed using official plugin documentation. Restores the “Custom Fields” meta box for the Gutenberg Block Editor. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Custom Fields for Gutenberg 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
Custom Fields for Gutenberg 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 Custom Fields for Gutenberg 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
- Restores the “Custom Fields” meta box for the Gutenberg Block Editor.
- Provides plugin options configurable via a settings screen.
- Allows specifying which post types should display custom fields.
- Supports excluding custom fields based on protected/hidden status, empty values, and/or specific custom field names.
- Implements usage behavior for editing, adding, and deleting custom fields via the Gutenberg editor (mirroring the original “Custom Fields” meta box workflow).
- On uninstall, removes plugin settings from the WordPress database, while leaving existing custom fields intact.
TRANSLATION BOUNDARY
Custom Fields for Gutenberg 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
Custom Fields for Gutenberg and REEID Translate FAQ.
What does Custom Fields for Gutenberg do?
Custom Fields for Gutenberg has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Custom Fields for Gutenberg 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 Custom Fields for Gutenberg?
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 Custom Fields for Gutenberg in a multilingual WordPress workflow.
REEID documents Custom Fields for Gutenberg 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.