W WPMMCC / Docs
简体中文

WPMMCC cross-site content sync

WPMMCC 1.0.0 copies content between WordPress sites you already run. It is not the translation plugin, and it does not use WPTSALL Client.

Need languages, not a second site? Install WPMMCC ATS. That plugin translates inside one site and can optionally use the local client. WPMMCC only syncs content you choose to a paired peer.

What it is

Install the plugin, open WPMMCC Sync in wp-admin, and pair another WordPress site. After that, changes move peer to peer. There is no account on wpmm.cc and no relay server. WordPress 6.2+ and PHP 7.4+ are required. The license is GPL-2.0-or-later. Source: github.com/wpmmcc/wpmmcc.

  • Point-to-point sync for standalone sites and multisite subsites.
  • Change capture with a short coalesce window, plus an hourly fingerprint check that repairs drift.
  • Images, video, audio, and documents move with the content.
  • Adapters cover common content plugins such as WooCommerce, Elementor, ACF, bbPress, Yoast SEO, and Rank Math.

Topologies

A peer can be a standalone site or one subsite in a network. These four pairings are supported:

  • Standalone to standalone
  • Subsite to subsite
  • Subsite to standalone
  • Standalone to subsite

The plugin refuses to pair a site with itself, so one install cannot loop its own content.

Pair a peer

  1. Upload wpmmcc to /wp-content/plugins/ and activate it.
  2. On the site that will accept the connection, open WPMMCC Sync and create a pairing code.
  3. On the other site, submit that remote URL and pairing code. The plugin sends one JSON POST to {remote}/wp-json/wpmmcc/v1/sync/handshake.
  4. The peer answers with its site UUID and a shared secret. That secret stays on the two sites and signs later requests. It is not sent to anyone else.

Nothing is sent until an administrator connects a peer, runs a sync or connection test, or the hourly reconciliation job runs for a peer that is already paired. Private and local peer addresses are refused unless an administrator opts in. Redirects are not followed.

What travels on the wire

Payloads are JSON signed with HMAC-SHA256. Requests carry X-WPMMCC-Site-UUID, X-WPMMCC-Timestamp, X-WPMMCC-Nonce, and X-WPMMCC-Signature. The plugin does not unserialize PHP objects from the wire.

  • /wp-json/wpmmcc/v1/sync/push and /sync/receipt — content changes and delivery receipts.
  • /wp-json/wpmmcc/v1/sync/digest and /sync/pull — identifiers used to pull content the peer already has.
  • /wp-json/wpmmcc/v1/sync/reconcile-digest — fingerprints compared by the hourly job.
Privacy: WPMMCC does not contact wpmm.cc, www.wpmm.cc, or any other vendor server. There is no phone-home, license check, telemetry, or language-pack download. The only outbound HTTP is to a WordPress site an administrator paired.