Outcome
Templates that rely on ACF render correctly on the target because their field definitions and related content structures moved with them.
Sync ACF Fields with Templates
Move ACF field groups, post types, taxonomies, and related templates as one change.
Video walkthrough
▶
Video walkthrough coming soon.
The YouTube embed will appear here.Risk level
Medium. Field definitions can affect editing screens and template rendering. Include dependent content carefully.
Before you start
- Identify field groups used by the template/page.
- Include ACF post types and taxonomies when the release introduces them.
- Confirm target environment has ACF active if the integration is required.
Steps
- Select the template/page changes
Start from the visible release item. - Add ACF integrations
Include ACF, ACF post types, and ACF taxonomies as needed. - Include content dependencies
Add pages, posts, categories, tags, or media when fields reference them. - Dry-run import
Look for missing post types, taxonomy terms, or conflicts. - Verify field output
Check front-end rendering and admin editing screens on the target.
Field IDs can differ between sites
Prefer deterministic field keys and include the field definitions in the same release as the templates that consume them.Integration basis
WPChangeSync includes manifests for ACF, ACF post types, ACF taxonomies, Meta Box, and ACPT.
$pathstringRequired
Absolute path of the directory to write the snapshot to.
$modestringOptionaldefault:
two-waySync direction — push, pull or two-way.
$gitboolOptionaldefault:
falseWhen true, commits the snapshot to the repository after writing.