ADVANCED CUSTOM FIELDS: MULTIPLE COORDINATES
Advanced Custom Fields: Multiple Coordinates compatibility with REEID Translate
Advanced Custom Fields: Multiple Coordinates compatibility with REEID Translate is being evaluated from available plugin evidence. Provides an ACF field type named “Coordinates map” for storing multiple Google Maps coordinate points (numbered points) within a single field value. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Advanced Custom Fields: Multiple Coordinates.
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
Advanced Custom Fields: Multiple Coordinates is documented in the Other category with 7 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 Advanced Custom Fields: Multiple Coordinates 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
- Provides an ACF field type named “Coordinates map” for storing multiple Google Maps coordinate points (numbered points) within a single field value.
- Point editing supports adding points by clicking the map, adding points via a search field (which stores a label for searched places), dragging points to move them, and removing points from an “Edit points” list.
- Preserves an explicit stored order for points; the stored order is used for the order returned by `get_field()` and for how line/area shapes are drawn.
- Supports drawing a shape through points when the saved value includes shape settings: none, Line, or Area; line/area rendering can be straight segments (“Sharp”), a Catmull-Rom smoothed curve (“Smoothed”), or a bounding box (“Bounding box”).
- Stores the field value as JSON in postmeta and keeps backward compatibility for existing saved values (editing-screen changes; data format remains usable via `get_field()`).
- Reads an existing Google Maps API key from ACF’s global setting `google_api_key`; if not set, a key can be provided via the `acfmc_gmaps_key` filter.
- Does not render anything on the front end; ACF’s `[acf field=
CONTENT BOUNDARY
Advanced Custom Fields: Multiple Coordinates 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
Advanced Custom Fields: Multiple Coordinates and REEID Translate FAQ.
What does Advanced Custom Fields: Multiple Coordinates do according to the available plugin evidence?
Advanced Custom Fields: Multiple Coordinates has 7 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 Advanced Custom Fields: Multiple Coordinates?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Advanced Custom Fields: Multiple Coordinates?
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 Advanced Custom Fields: Multiple Coordinates in a multilingual WordPress workflow.
REEID documents Advanced Custom Fields: Multiple Coordinates 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.