Templates, components, pages, posts, media, menus, widgets, categories, tags, ACF field groups, ACF post types, ACF taxonomies, ACPT, MetaBox, Gutenberg patterns, Bricks settings, and CSS frameworks can be handled as structured integrations.
Select specific items instead of pushing an entire site section.
Group templates, components, settings, and content into reusable job definitions.
Generated manifests keep item labels, slugs, hashes, and versions inspectable.
WPChangeSync is designed for the space between full-site cloning and manual copy-paste: selected templates, components, fields, pages, media, menus, settings, remotes, and workflows that can be reviewed and repeated.
Keep production content, users, orders, and environment-specific data out of the release when they are not part of the change.
Inspect export files, run dry-runs, and choose conflict behavior before production writes.
Use named workflows, webhooks, and scripts instead of remembering manual steps.
Skip, overwrite, duplicate, use newer, backup then overwrite, merge, or prompt per item. Review diffs and make high-risk decisions explicitly.
Conflicts can be queued and resolved by a human instead of during an automated run.
Field-level and Bricks element-tree merges help avoid throwing away target-side work.
Snapshots are stored before overwrites so teams can recover quickly.
WPChangeSync records actor, action, target, context, status, message, summaries, and detailed data with filterable queries and exportable CSV/JSON logs.
Record user, login, IP, remote ID, workflow ID, and operation ID.
Export selected audit windows for review, handoff, or client reporting.
Retention policies keep logs useful without growing forever.
Posts, pages, menus, widgets, media, categories, tags, and auto-discovered custom post types and taxonomies — plus custom fields from ACF, Meta Box, and ACPT. When Bricks is installed, templates, components, settings, and global styles come along too.
Combine options, custom tables, post types, and taxonomies into one Library group without writing code. Developers can export any source as a shippable integration — a JSON config or a wpchangesync_register_integration() snippet.
Deferred background downloads and per-item media pushes reduce gateway timeout risk.
Batch and workflow locks protect counters and state during cron/AJAX processing.
Stale JSON cleanup, manifest management, and runtime cleanup tools reduce drift.
WPChangeSync combines authenticated remotes, REST hardening, safe import handling, dry-runs, conflict strategies, backup snapshots, restore paths, and audit records so teams can move faster without hiding risk.
Use HTTPS, application passwords, capability checks, sanitized remote errors, and shared rate limiting.
Create snapshots before overwrites and restore known-good versions when imports go wrong.
Track workflow runs, approvals, imports, exports, validation failures, and restore activity.
