IMPORTLY FIELD MAPPER FOR ACF
Importly Field Mapper for ACF compatibility with REEID Translate
Importly Field Mapper for ACF compatibility with REEID Translate is being evaluated from available plugin evidence. Integrates into WP All Import Step 3 mapping/template flow by adding an ACF mapping step (“ACF Fields (Free)” section). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Importly Field Mapper for ACF.
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
Importly Field Mapper for ACF 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 Importly Field Mapper for ACF 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
- Integrates into WP All Import Step 3 mapping/template flow by adding an ACF mapping step (“ACF Fields (Free)” section).
- Detects ACF field groups and fields using `acf_get_field_groups()` and `acf_get_fields()` to drive available mapping targets.
- Stores ACF field mappings in WP All Import import options/templates.
- Updates ACF values during import using `update_field()`.
- Supports importing common ACF free field types including text, number, checkbox, true/false, date picker, image URL, and file URL.
- Handles media URLs for image/file with sideloading during the import process.
- Provides a debug logging mode for troubleshooting import/mapping issues.
- Can update ACF values for public custom post types (not limited to posts/pages).
CONTENT BOUNDARY
Importly Field Mapper for ACF 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
Importly Field Mapper for ACF and REEID Translate FAQ.
What does Importly Field Mapper for ACF do according to the available plugin evidence?
Importly Field Mapper for ACF 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 Importly Field Mapper for ACF?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Importly Field Mapper for ACF?
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 Importly Field Mapper for ACF in a multilingual WordPress workflow.
REEID documents Importly Field Mapper for ACF 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.