UWH Site Migrator – WP Migration, Backup & Restore
| 开发者 | unitedwebhost |
|---|---|
| 更新时间 | 2026年11月2日 14:41 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
United Web Host Site Migrator helps WordPress administrators create full-site backups, restore completed backup packages, move sites between WordPress installations, and optionally send backups to Google Drive.
The plugin is designed around resumable jobs and recovery controls so larger backups and migrations can continue in smaller steps instead of relying on one long browser request.
Features
- Full WordPress files and database backup packages using the .uwh package format, including all WordPress-prefixed tables such as posts, postmeta, theme, and page-builder settings.
- Local restore with resumable processing and integrity checks.
- Direct Site-to-Site Migration using an expiring migration key and HTTPS server-to-server transfer.
- Optional pre-restore safety checkpoints with automatic rollback support when enabled.
- Automatic scheduled backups.
- Optional Google Drive upload, inventory, import, and retention controls.
- Overview dashboard with local/cloud backup status and scheduling information.
- Troubleshooting diagnostics and downloadable diagnostic reports.
- Activity logs for backup, restore, rollback, Drive, scheduling, and migration events.
- Compatibility migration for Site Migrator 2.1.x settings and scheduled jobs when upgrading from the 2.1.x line.
安装:
- Upload the
uwh-site-migratorfolder to/wp-content/plugins/, or install the plugin ZIP from the WordPress Plugins screen. - Activate United Web Host Site Migrator.
- Open Site Migrator > Overview.
- Use Import / Export to create or restore local backups.
- Optional: open Drive Settings to connect Google Drive.
- Optional: open Direct Migration on both the source and destination site to perform a server-to-server migration.
屏幕截图:
常见问题:
What is stored inside a Site Migrator backup?
A full backup can contain WordPress files and database data required to restore or migrate the site. Treat backup files as sensitive data and store them securely.
Does Site Migrator support large sites?
Backup, restore, Drive transfer, and Direct Migration workflows use chunked or resumable processing where applicable. Actual limits still depend on available disk space, PHP/server limits, WordPress hosting configuration, and remote service limits.
Can I restore a backup created by Site Migrator 2.1.x?
Version 2.4.6 keeps the .uwh package format and includes compatibility handling for existing Site Migrator 2.1.x settings, schedules, and unfinished restore state.
Does the plugin require Google Drive?
No. Google Drive is optional. Local backup, local restore, and local migration workflows can be used without connecting Google Drive.
What happens before a destructive restore?
Restore safety checkpoints are optional and enabled by default. On the Import / Export and Direct Migration screens, Create restore safety checkpoint is preselected to back up the current destination site before it is replaced; you can uncheck it to skip the checkpoint. When enabled, that checkpoint may be used for automatic rollback if the restore fails during protected phases. When unchecked, restore starts directly without an additional checkpoint, and automatic rollback is unavailable. This does not bypass backup integrity checks or resumable restore steps. Existing checkpoints remain available in the recovery interface.
Why can a database backup report that a source table changed?
Live WordPress sites can add postmeta, scheduler or other rows during a resumable database export. Site Migrator preserves all core, Elementor/theme and plugin tables; it does not remove postmeta or unknown plugin tables simply to bypass this warning. New backups capture a stable high-water key per table when the table uses an indexed, integer auto-increment primary key. Records added after that boundary are reported as a warning rather than wrongly treated as missing original rows. Changes to previously existing rows are not covered by a single site-wide transaction. Pause content edits, jobs and source database writes during a critical migration backup if a consistent point-in-time copy is required. For backups begun before this fix, start a new backup to apply the new boundary logic.
Does Site Migrator support WordPress Multisite?
No. The current release is intended for standard single-site WordPress installations.
更新日志:
2.5.0
- Plugin Check compliance: improve error escaping and translation comments, document essential native ZIP/locking stream operations, and use WordPress filesystem helpers where suitable.
- Preserve the original plugin directory listing name and existing backup, restore, migration, and Fast ZIP functionality.
- Experimental, opt-in append-only ZIP64 writer for new MANUAL backups. This avoids repeatedly rewriting a growing ZIP central directory during file archiving. It is disabled unless
UWHSM_EXPERIMENTAL_STREAM_ZIPis set to true in wp-config.php. - Commit an archive byte offset and private entry-journal offset with each saved batch. On interrupted requests, discard uncommitted trailing data and resume from the prior state. Write one standard ZIP64 central directory at backup completion, then verify it with ZipArchive before marking complete.
- Keep the established .uwh manifest, database, and integrity.json metadata structure; preserve the legacy ZipArchive code path for all existing jobs, restore checkpoints, and scheduled automatic backups.
- This is a development/test release, not recommended as a WordPress.org production update until real-site end-to-end backup/restore and multi-host testing succeeds. ZIP64 archives larger than 4 GB have not yet been bench-tested in this test environment.
- Step 3: Avoid opening/updating large ZIP packages during skip-only archiving batches; preserve last real ZIP-close timing for safe adaptive tuning. Maintain existing .uwh archive entries, compression modes, SHA-256 integrity, and restart behavior.
- Step 4: Stream serialized database rows in bounded 256 KiB buffers with complete short-write handling; keep exact base64-serialized rows, committed byte offsets and resumable keyset/offset cursors unchanged.
- Build final database inventory in one pass, validating staged schema/row files before the ZIP queues them. Preserve all WordPress-prefix tables and existing restore compatibility.
- No changes to Direct Migration, restore, Google Drive, background scheduling, Pause/Resume/Stop, Elementor, or maintenance behavior.
- Record bounded ZIP file-batch performance diagnostics: archive opening, SHA-256 checksum reads, ZIP entry queue, closing, total request time, input throughput, file count and batch limits. View the last 8 samples in Troubleshooting and download them in the diagnostic report.
- Tune file-archiving batches conservatively using real elapsed processing time, ZIP close cost, checksum overhead, recent throughput and file count. Fall back to the previous safe limits for older backup jobs without measurements.
- Preserve the existing .uwh format, database export, checksum integrity, resume/pause/stop, background processing, migration, restore and Google Drive behavior.
- Improve reliability of background backups when administrators switch tabs or close the browser: recover missing scheduled events and retry transient failures with limits.
- Use adaptive file and database batches to reduce backup processing overhead on varied servers, retaining integrity and resume protection.
- Preserve existing backup, restore, direct migration, Google Drive, maintenance and recovery functionality.
- Allow final verification to finish if the specific host-managed
.private/.htaccesswas removed or rewritten after restore; record a security warning requiring destination access-control review. - Keep all other file-integrity checks, archive checks and restore features unchanged.
- Treat
.htaccess.bkas an optional inactive server configuration backup copy during backup, restore and final file verification. Existing archives and paused verification jobs can complete when this nonessential copy is missing or altered. - Preserve full checksum verification for all required website files, database and Elementor settings, active server configuration safety, Direct Migration, and resumable restore.
- Restore v2.4.5-style Elementor finalization: avoid reprocessing imported template postmeta at 99% while retaining database/file integrity and template-presence checks. Previously interrupted jobs can resume without the retired verification step.
- Improve cross-domain restore finalization by preserving malformed source serialized values rather than rewriting their invalid string lengths. Valid serialized settings continue to be rewritten with correct byte lengths.
- Retain Direct Migration, backup/restore, Google Drive, Skip Missing Plugins, and recovery functionality.
- Add explicit administrator-approved Skip & Resume for orphaned active plugin entries missing from a Direct Migration archive. Skipped plugins remain inactive at the destination; all database, theme and file integrity checks remain enforced.
- Source-first post-restore processing: preserve imported Elementor Theme Builder conditions and source logo identity; only rebuild missing conditions cache.
- Restore cache refresh remains deferred until source plugins load; previous incomplete restore jobs keep their earlier recovery behavior.
- Preserve WordPress core Site Logo references, reconcile Elementor Site Identity image URLs after migration, and provide logo diagnostics and a guarded manual repair.
- Verify WordPress Custom Logo, Site Icon and Elementor Site Identity attachment files during migration. Restore source custom logo setting when changed during transfer.
- Process larger but CPU/memory-bounded batches during final slug and builder-template verification.
- Fixed restore state progression from database import into the required resumable template and permalink verification phase.
- Existing paused 99% restore jobs can resume verification without starting a new migration.
- Clearer step labels during large template and slug verification.
- Rebuild Elementor Pro Theme Builder display conditions after migration, in addition to Elementor CSS.
- Add read-only Elementor template diagnostics and safe manual repair in Troubleshooting.
- Preserve original header/footer condition cache if regeneration fails or drops assigned templates.
- Preserve source page/post and taxonomy slugs, and source permalink settings during cross-domain restore.
- Verify restored Elementor header/footer metadata and display conditions before completion.
- Confirm missing or changed template metadata rather than reporting a false successful migration.
- Keep destination credentials active until the database, homepage, theme and site identity pass verification; publish the restored users/usermeta tables together at finalization.
- Preserve valid empty tagline settings and recreate only archive-verified site identity option rows when genuinely absent.
- Retain import receipts until the completed restore is durably saved; support safe retries and older interrupted restore states.
- Avoid false postmeta import failures when WordPress adds rows during an interrupted or long-running migration: verify every archived postmeta row and its content before accepting extra runtime rows.
- Restore the source active parent/child theme when the destination default theme changes the saved options during migration. Verify source backup theme options against archived database rows and validate theme file checksums before activation. Keep incomplete restore recovery resumable.
- WordPress.org release version updated; migration, database export, backup/restore, recovery, and no-file-staging logic remain unchanged from the final 2.4.10 package.
- Added authoritative source Reading Settings snapshot and verified restored homepage options and referenced page.
- Verify physical imported table row counts before a restore is declared complete; fail safely on mismatches.
- Keep existing .uwh archives readable and retain backup/restore, Drive and Direct Migration features.
- Added optional per-operation restore safety checkpoints for uploaded, local and direct restores. With the option disabled, restores skip the pre-restore backup and automatic rollback is unavailable.
- Validate source active and parent theme files before restore; verify restored theme settings and files before reporting completion.
- Queue an automatic, deferred Elementor CSS cache refresh and soft permalink refresh after migration.
- Rewrite alternate HTTP/HTTPS source URLs in migrated data, preserving serialized values.
- Improved responsive layouts on desktop, tablet and mobile, including long filenames, navigation, cards and scrollable tables.
- Improved restore confirmation keyboard accessibility and restore file selection feedback.
- Preserve .uwh backup filenames when downloading on mobile by serving local backups as binary attachments with an explicit .uwh filename.
- Harden Google Drive backup row rendering against malicious file names.
- Preserve WordPress core maintenance files owned by independent updates.
- Close archive handles on checksum failures without altering backup contents.
- Prevent uninstall cleanup from following unsafe or symlinked backup storage overrides.
- Restrict legacy background schedule migration to Site Migrator admin pages to reduce unrelated wp-admin I/O.
- Guard against unsafe legacy/custom backup storage paths that could block access to WordPress.
- Retain all previously merged backup, migration, selected-file and recovery improvements.
- Keep one server-backed progress indicator across Site Migrator screens; reconcile lost or invalid responses with the saved backup job.
- Use smaller database batches to reduce request timeouts, and preserve resumable jobs after refresh.
- Improve restore upload UX with a prominent selected-backup card, filename, size and remove action.
- Retain transferred source backups after Direct Migration while keeping restore checkpoints separate.
- Isolate WPvivid, All-in-One WP Migration and other external backup repositories from Site Migrator backup/restore file inventory.
- Avoid interfering with third-party plugin AJAX operations and maintain WordPress.org code checks for recovery requests/scripts/schema metadata.
- Keep safer login-independent restore recovery and directory compatibility updates from earlier releases.
- Preserve the live options table during staging, then atomically switch while retaining the destination uploads settings.
- Provide token-protected, login-independent restore resume from the original browser.
- Retain restore maintenance guard until the completed job is durably saved; detect already completed state.
- Keep Google Drive, Direct Migration, custom paths and non-InnoDB support from 2.4.5.
- Updated release version metadata to 2.4.5; no changes to backup, restore, Drive, or migration behavior.
- Fixed Google Drive Connect after the safe-redirect compliance change by temporarily allowlisting only the trusted Site Migrator OAuth gateway host during authorization redirects.
- Fixed the final Plugin Check slow-query false positive in restored usermeta row rewriting without changing migration behavior.
- Fixed Direct Site-to-Site Migration restore failures caused by runtime WordPress options being recreated between resumable database restore batches.
- Compatibility migrations now stay read-only during restore-step requests so partially restored
wp_optionsdata is not mutated between batches. wp_optionsrows from the source backup are authoritative during restore and safely replace duplicate runtime-created option keys; other database tables keep normal insert behavior.- Includes the WordPress.org review hardening from the 2.4.1 line: scoped admin assets, sanitized request handling, encrypted Drive state/options, no generated MU-plugin loader, clean activation without ZipArchive, and HTTPS-only Direct Migration.
- Scheduled-backup startup failures now stay in Site Migrator Activity Logs instead of writing a duplicate raw PHP server error log.
- Cleaned the reported Plugin Check warning set by centralizing sanitized request reads, using safe redirects, and documenting intentional low-level database/streaming operations without changing backup, restore, Drive, or Direct Migration workflows.
- Fixed resumable Direct Site-to-Site Migration restores that could collide with live WordPress option rows between database batches; restore-step boot is now isolated from compatibility option/cron migration and source wp_options rows safely replace runtime collisions.
- Addressed WordPress.org review findings by enqueueing admin CSS on plugin screens, tightening request sanitization/authorization, and allowing clean activation when ZipArchive is unavailable.
- Replaced dynamically generated restore MU-plugin code with an in-plugin restore guard and maintenance response during destructive restore phases.
- Moved Google Drive connection and in-progress transfer state to encrypted WordPress options; existing legacy Drive configuration is migrated on first read.
- Renamed the WordPress.org plugin identity to United Web Host Site Migrator with the
uwh-site-migratorslug while preserving existing UWHSM compatibility keys and internal data paths. - Added explicit Site Migrator, United Web Host, and Google Privacy/Terms links to the External Services disclosure for Plugin Directory review clarity.
- Removed the global upgrader download interception while retaining the normal upload prefilter and installer-side
.uwhguidance. - Removed the admin hosting promotion and duplicate View details link; the remaining Plugin Website link now points to the public Site Migrator website.
- Improved plugin upload/overwrite compatibility on hosting platforms with aggressive ModSecurity/Imunify-style archive scanning.
- Removed uninstall-time raw database table deletion and preserved interrupted restore progress tables as recovery state.
- Switched uninstall temporary filesystem cleanup to WordPress' direct filesystem API while retaining strict path allowlists and preserving settings, backups, checkpoints, and Drive configuration.
- Added a guarded WordPress uninstall handler that removes only runtime/log/temp state while preserving Site Migrator settings/options, encrypted Google Drive configuration, completed local backups, restore/rollback checkpoints, and remote Drive backups.
- Added cleanup for activity logs/deduplication state, Direct Migration sessions, Site Migrator cron hooks and Drive-notice transients, exact temporary restore-progress tables, job/import/Drive-transfer/direct-pull state, locks, staging database files, and the temporary restore MU-plugin loader.
- Added strict preservation guards so broad
uwhsm_*/svm_*option or database deletion is not performed during uninstall. - Improved PHP readability and WordPress Coding Standards alignment across core classes, including expanded control flow, consistent indentation/spacing, clearer one-statement-per-line formatting in high-risk runtime code, and safer superglobal unslash/sanitization paths.
- Kept the
.uwhformat, admin slugs, AJAX/cron identifiers, Google Drive storage format, Direct Migration wire protocol, and restore/rollback behavior unchanged.
- Replaced the remaining raw cURL Drive download path with the WordPress HTTP API using safe streamed downloads to disk.
- Added full PHP admin/runtime internationalization using the
site-migratortext domain. - Added native JavaScript translations through
wp.i18nandwp_set_script_translations(). - Added
languages/uwh-site-migrator.potfor translation tooling. - Preserved the
.uwhpackage format, existing admin slugs,uwhsm_*routes, and Direct Migration wire compatibility.
- Renamed plugin-owned PHP, WordPress hook/action, option, cron, nonce, and browser-global prefixes to
UWHSM_/uwhsm_. - Added an explicit backward-compatibility layer for Site Migrator 2.1.x options, scheduled events, legacy request routes, existing Direct Migration sessions, and unfinished restore progress tables.
- Kept the existing
.uwhbackup format, backup filenames, plugin slug, admin page slugs, and Direct Migration wire key/header protocol unchanged. - Converted
readme.txtto the WordPress Plugin Directory format. - Added GPLv2-or-later metadata and the full GNU GPL version 2 license text.
For older release history, see
CHANGELOG.txtincluded with the plugin.