Dragon Migrate

A quiet pointer to the Pro add-on: an Upgrade to Pro link on the Plugins screen, a one-line note at the foot of the plugin's screens, and a single dismissible notice once the plugin has done its job. Nothing in the free plugin is locked or changed, and all three disappear when Pro is active.

• The Pro tab now links to the Dragon Migrate Pro page.

Full-site archives now fail loudly, and name the file, instead of silently leaving files out when the file list cannot be written.

What's fixed in 1.0.10

• An archive that cannot write its file list fails instead of pretending. While a full-site archive lists files it writes them to a manifest on disk. If that write could not be opened or was cut short (a full disk is the usual cause), the archive used to carry on, skip the affected files, and report "Archive complete." with them missing. The job now stops with a clear error.
• Unreadable manifest entries are counted and named. A manifest line that cannot be read is now included in the "files could not be read" total and written to the job log with the entry text, so you can see exactly which file is not in the archive.
• File names that cannot be listed are counted too. A file whose name cannot be represented in the manifest is reported in the job log with its path rather than dropped silently.

No settings or data changes.

Dragon Migrate now asks for a WordPress.org review once, on its own screen, after your first completed job.

What's new in 1.0.9

• One-time review prompt. After an export, import, archive or find-and-replace job completes, the Migrate screen shows a short request for a WordPress.org review. "Maybe later" hides it for a month and "No thanks" hides it for good. It never appears anywhere else in wp-admin.
• New dragonmigrate_job_complete action fires when a job finishes, with the job id and type.
• The plugin directory listing now describes what the plugin does in its title and tags, so it is easier to find.

No behaviour, settings or data changes otherwise.

Major reliability release: imports now survive replacing your login session mid-migration, phpMyAdmin-style dumps import correctly, and the progress bar finally moves.

Imports

• A migration now carries its own credential, so a large import that replaces the database (and with it, your login session) drives itself to completion instead of stranding half-applied. When that happens you're told to log back in with the imported site's admin credentials — your automatic pre-import backup is on the Backups tab.
• Dumps made of many small statements — phpMyAdmin exports, mysqldump --skip-extended-insert — no longer fail part-way through.
• Importing a dump whose tables use a different prefix now says so plainly instead of reporting a success that changed nothing.
• Batch boundaries can no longer drop characters from imported content, and dumps containing triggers or stored routines are refused with a clear message rather than corrupted.
• The import/restore progress bar now reflects real progress.

Search & replace

• Only genuinely textual columns are touched — numbers, dates, and binary data are no longer rewritten (searching for "2026" no longer edits your post dates).
• Tables with composite keys (like term relationships) are now processed instead of skipped.
• Values that can't be safely rewritten are counted and reported instead of silently passed over, and rows the search never matched are never rewritten.

Exports, backups & archives

• Row ordering is now deterministic on every table shape, generated columns are recomputed on the destination instead of breaking the restore, and database views are excluded (and announced) rather than producing a dump that can't restore.
• A full disk during an export, archive, or restore is detected instead of producing a silently truncated file.
• Abandoned jobs clean up after themselves, and retention pruning can no longer delete a backup that a queued restore is about to use.
• Archives skip symbolic links entirely and report any files they couldn't read.

Other fixes

• The Profiles tab's "Use" button now applies the profile.
• WP-CLI: plain-SQL export works via the new --uncompressed flag, and an empty table selection is refused instead of claiming success.

Security hardening: blocks PHP object injection when running search-replace over imported data.

= 1.0.7 =

• Security: serialization-safe search-replace no longer instantiates arbitrary classes from imported data (object-injection hardening); ordinary data still migrates unchanged.
• Hardening: authenticated encryption for stored secrets.

Refreshed the shared admin design kit.

• Housekeeping: refreshed the shared admin design kit stylesheet.

Dragon Migrate is now tested and verified on WordPress 7.1.

• Compatibility: fully tested on WordPress 7.1 — export, find-replace and housekeeping verified on the latest release.
• Housekeeping: job-history pruning queries now use WordPress's built-in identifier placeholder for extra safety.

Deleting a backup now asks for confirmation naming the exact file — it was previously one click and unrecoverable. Finished job history is also pruned automatically after 60 days.

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.

A cleaner, consistent look: the Dragon design system arrives.

This release brings Dragon Core's design system to every screen: a consistent header with the Dragon mark, cleaner tables, and unified status colours across the whole plugin family. Purely visual — everything behaves exactly as before.