CUSTOM FIELDS MISSING WHEN ACF IS ACTIVE
Custom Fields Missing When ACF is Active compatibility with REEID Translate
Custom Fields Missing When ACF is Active compatibility with REEID Translate is being reviewed using official plugin documentation. Reverses ACF’s behavior that hides/removes the native WordPress Custom Fields meta box on post/page/CPT edit screens when ACF (or ACF Pro) is active. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Custom Fields Missing When ACF is Active 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 Missing When ACF is Active is documented in the Other category with 4 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 Missing When ACF is Active 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
- Reverses ACF’s behavior that hides/removes the native WordPress Custom Fields meta box on post/page/CPT edit screens when ACF (or ACF Pro) is active.
- Restores visibility of the native WordPress Custom Fields when the ACF plugin is disabled (i.e., the plugin targets the ACF-active state).
- Targets the admin edit UI behavior introduced by ACF starting with version 5.5.13 and made default in 5.6.0 (per the plugin’s own description).
- Provides a “reverse” workaround so users do not need to edit theme code (e.g., function.php) to restore the native custom fields UI (per the plugin’s own description).
TRANSLATION BOUNDARY
Custom Fields Missing When ACF is Active 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 Missing When ACF is Active and REEID Translate FAQ.
What does Custom Fields Missing When ACF is Active do?
Custom Fields Missing When ACF is Active has 4 documented features listed in its official documentation. See the Plugin Information section for details.
Does Custom Fields Missing When ACF is Active 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 Missing When ACF is Active?
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 Missing When ACF is Active in a multilingual WordPress workflow.
REEID documents Custom Fields Missing When ACF is Active 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.