WP Manifestindependent plugin directory
manifest / updates / veravalonline-failover-post-sync

VO-Solo-Post-Sync

Sync WordPress blog posts, images, and metadata to a failover server over DNS or IP without changing public URLs.

by VO WordPress · github.com/vopvtltd/veravalonline-failover-post-sync · website

★ 0stars

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/vopvtltd/veravalonline-failover-post-sync/archive/refs/heads/main.zip
No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.
Readme github.com/vopvtltd/veravalonline-failover-post-sync ↗

Sync WordPress blog posts, images, and metadata to a failover server over DNS or IP without changing public URLs.

Description

Use this when the same site (for example riveroaksmri.com/blogs) runs on Server A and a standby Server B. Publishing on A used to leave B stale, which hurts SEO after DNS failover.

Install the plugin on both WordPress copies. The primary pushes:

  • Post title, slug, content, excerpt, status, and exact publish/modified dates
  • Featured images and attached media, written to the same uploads path
  • Categories, tags, and custom taxonomies
  • SEO and custom field metadata (Yoast, Rank Math, ACF, and others)
  • Deletes or trash, if enabled

Visitor-facing URLs stay on the public domain. The plugin never rewrites content to the failover IP or internal hostname.

Installation

  1. Copy the vo-solo-post-sync folder into wp-content/plugins/ on Server A and Server B.
  2. Activate VO-Solo-Post-Sync on both sites.
  3. On both sites, open VO Solo Post Sync → Settings and paste the same Shared API key.
  4. Server A: role = Primary. Set Destination URL to Server B’s WordPress home URL.
  5. Server B: role = Failover.
  6. On Server A click Test connection, then Sync all posts once to seed B.

DNS mode: Destination URL is a hostname that already points at Server B (internal DNS, hosts file, or a dedicated failover name).

IP mode: Destination URL is the public HTTPS URL (https://riveroaksmri.com or https://riveroaksmri.com/blogs). Destination IP is Server B. Requests keep the real Host/SNI so the SSL certificate still validates.

Frequently Asked Questions

Will this change permalinks or image URLs?

No. Slugs and upload relative paths are copied as-is. Public URLs stay on the visitor domain.

Do post IDs stay the same?

Not necessarily. Matching uses a hidden sync GUID, then the same slug. Gutenberg image IDs and attachment meta are remapped automatically.

What if we already created some posts by hand on Server B?

A full sync updates the failover post that has the same slug, so you do not get duplicates.

Changelog

1.0.0

  • Initial release.