ACF POST-2-POST
ACF Post-2-Post translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what ACF Post-2-Post does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Adds automatic bidirectional (two-way) synchronization for ACF Relationship and Post Object fields, updating the related post’s field when the edited post is added/removed from the relationship.
- Requires ACF >= 5 to provide functionality; it will not work with ACF Version 4 and provides no functionality if ACF >= 5 is not installed.
- Does not create new field types or provide an admin interface; it operates on existing ACF Relationship and Post Object fields.
- Field constraints for bidirectional behavior: the ACF field must be top-level (not a subfield of repeater/flexible content) and the field name must match across the involved post types.
- Supports Post Object fields with multiple values similarly to Relationship fields; for single-value Post Object fields, it can overwrite existing values when configured via overwrite settings.
- Provides an overwrite-settings mechanism (via the `acf-post2post/overwrite-settings` filter) to control behavior when the related field already has reached its maximum number of values (overwrite true/false and first/last removal).
- Allows disabling automatic bidirectional updates for specific field keys via the `acf/post2post/update_relationships/key=field_XXXXXXXX` filter returning false.
- Exposes post-update hooks: `acf/post2post/relationship_updated` (runs after each related post update, receives a single post ID) and `acf/post2post/relationships_updated` (runs after all related posts are updated, receives an array of post IDs).
Distinctive features
Adds automatic bidirectional (two-way) synchronization for ACF Relationship and Post Object fields, updating the related post’s field when the edited post is added/removed from the relationship. Requires ACF >= 5 to provide functionality; it will not work with ACF Version 4 and provides no functionality if ACF >= 5 is not installed. Does not create new field types or provide an admin interface; it operates on existing ACF Relationship and Post Object fields. Field constraints for bidirectional behavior: the ACF field must be top-level (not a subfield of repeater/flexible content) and the field name must match across the involved post types. Supports Post Object fields with multiple values similarly to Relationship fields; for single-value Post Object fields, it can overwrite existing values when configured via overwrite settings. Provides an overwrite-settings mechanism (via the `acf-post2post/overwrite-settings` filter) to control behavior when the related field already has reached its maximum number of values (overwrite true/false and first/last removal). Allows disabling automatic bidirectional updates for specific field keys via the `acf/post2post/update_relationships/key=field_XXXXXXXX` filter returning false. Exposes post-update hooks: `acf/post2post/relationship_updated` (runs after each related post update, receives a single post ID) and `acf/post2post/relationships_updated` (runs after all related posts are updated, receives an array of post IDs).
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what ACF Post-2-Post does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
ACF Post-2-Post and REEID Translate FAQ.
Does the current evidence establish translation scope for ACF Post-2-Post?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.