Dragon Migrate Pro

Your licence now keeps working after it lapses. Pro features stay on for every activated site; renewing restores updates and support on the same key.

• The licence screen shows Lapsed, and what that means, instead of a red Expired.
• New versions are fetched only while the licence is current. Nothing else changes.

File sync now names every file it could not list, and sites on non-ASCII domains pair correctly.

What's fixed in 1.0.10

• File sync no longer reports a file it could not list as delivered. If a file could not be added to the sync's work list (a file name the database rejects, for instance), it landed in no bucket and the sync still said "File sync complete". Such files are now counted separately and each one is named in the job log with the database's reason, so you can see exactly which files were not sent. The completion message says how many could not be listed.
• Internationalised domains pair. Connecting to a site whose domain contains non-ASCII characters failed with "The connection host is not allowed", because the host was looked up without converting it to its DNS form. It is now converted before it is resolved, checked and pinned; ASCII hosts are handled exactly as before.
• A pairing address containing a username or password is refused. Such an address is never needed to pair two sites, and because the credential part can be written to look like a host name, accepting one risked checking one host and connecting to another. Any connection address with credentials in it is now rejected outright.

No settings or data changes.

Paired sites no longer have to run the exact same release to transfer — they only need to speak the same transfer protocol.

Previously, preflight refused any transfer between two sites on different plugin versions. With automatic updates, two paired sites rarely update at the same moment, so every release opened a window where a scheduled overnight staging refresh simply failed until both sites had caught up.

Preflight now checks the transfer protocol version instead. Ordinary releases don't change it, so transfers keep working across an update gap — you'll just see a note that the versions differ. A release that genuinely changes how the two sites talk to each other will say so in its changelog, and only then do both ends need updating together.

Preflight also now mentions when the two sites run different versions of the free Dragon Migrate plugin, purely for context — free dumps stay importable across versions.

One transition note: this new rule takes effect on the site that starts the transfer. A site still on 1.0.8 or earlier applies the old strict check when it initiates, so update both ends this one time — after that, update gaps no longer interrupt transfers.

Reliability release for site-to-site transfers: a failed pull now rolls itself back, and your licence and schedules survive an incoming transfer.

Transfers

• A pull that fails part way through now restores the automatic restore point it took beforehand, instead of leaving the site half-transferred. Incoming pushes already behaved this way; pull now matches them.
• A transfer is refused outright if its restore point is missing, rather than applied with no way back.
• Progress is now accurate for push, pull and file sync. A push used to run past 100%, and a file sync where everything was already up to date sat at 0% from start to finish.

Your site's own settings survive

• Your Pro licence is no longer overwritten by an incoming transfer, so Pro keeps working on the receiving site instead of quietly switching itself off.
• Scheduled transfers keep running after a push or pull. The incoming database used to bring the sending site's schedule with it and replace the destination's.

Other fixes

• File sync tables are created on activation, so WP-CLI and scheduled syncs work on a site whose admin screens have never been opened.
• The audit log keeps the specific reason a transfer ended (for example "import failed, rolled back") instead of overwriting it with a generic message.
• A failed transfer no longer leaves its internal sub-job sitting at "running".

Requires the free Dragon Migrate 1.0.8 or later.

Security update: hardens file sync and site-to-site transport against remote-code and SSRF risks.

= 1.0.7 =

• Security: file sync refuses server-config files (.user.ini/.htaccess/web.config) in uploads; site-to-site push requires HTTPS for public targets and pins the connection to the validated IP (DNS-rebinding SSRF hardening).
• Hardening: authenticated encryption at rest; a stored licence is re-checked for a usable key before trusting the cached result.

Tested and verified on WordPress 7.1.

• Compatibility: tested up to WordPress 7.1.

The licence check no longer touches front-end page loads, scheduled transfers resume across cron runs instead of holding a worker for hours, overlapping schedule runs are prevented, and removing a connection or schedule now asks for confirmation.

Your data now survives uninstall by default.

Uninstalling no longer deletes the plugin's data unless you explicitly opt in first, so removing it to debug — or coming back later — keeps everything intact. Where the plugin has a settings screen you'll find a new "Delete all data on uninstall" option; leave it off to keep your data.