Title: かんたんお引越し for お名前.com Author: Onamae.com byGMO Published: 25. měrca 2019 Last modified: 29. julija 2026 --- Tykace pytaś ![](https://ps.w.org/wp-migration-for-onamaecom/assets/banner-772x250.jpg?rev=3406528) ![](https://ps.w.org/wp-migration-for-onamaecom/assets/icon-256x256.jpg?rev=3406528) # かんたんお引越し for お名前.com Wót [Onamae.com byGMO](https://profiles.wordpress.org/onamaecom/) [Ześěgnuś](https://downloads.wordpress.org/plugin/wp-migration-for-onamaecom.2.1.5.zip) * [Drobnostki](https://dsb.wordpress.org/plugins/wp-migration-for-onamaecom/#description) * [Pógódnośenja](https://dsb.wordpress.org/plugins/wp-migration-for-onamaecom/#reviews) * [Instalacija](https://dsb.wordpress.org/plugins/wp-migration-for-onamaecom/#installation) * [Wuwiśe](https://dsb.wordpress.org/plugins/wp-migration-for-onamaecom/#developers) [Pódpěra](https://wordpress.org/support/plugin/wp-migration-for-onamaecom/) ## Wopisanje This plugin enables the „Easy Migration“ feature for WordPress on Onamae.com Rental Server. It allows you to migrate a WordPress site running on another server to your Onamae. com Rental Server. #### Target Users This plugin is available free of charge for Onamae.com Rental Server subscribers. To use the plugin, you need to enter the source WordPress site information from the Onamae.com Rental Server control panel. Please note that this plugin will not function on servers other than Onamae.com Rental Server. #### Support For usage instructions, please refer to the Onamae.com Rental Server user guide. Onamae.com Rental Server Guide: https://www.onamae-server.com/guide/rs/ ## Instalacija This plugin requires an active Onamae.com Rental Server subscription. The plugin is automatically installed when you initiate the „Easy Migration“ process from the Onamae.com Rental Server control panel. ## FAQ For frequently asked questions, please refer to the Onamae.com Help Center. Onamae.com Help Center: https://www.onamae.com/help/ ## Reviews There are no reviews for this plugin. ## Sobustatkujuce a wuwijarje „かんたんお引越し for お名前.com“ jo software wótwórjonego žrědła. Slědujuce luźe su pśinosowali k toś tomu tykacoju. Sobustatkujuce * [ Onamae.com byGMO ](https://profiles.wordpress.org/onamaecom/) [Translate “かんたんお引越し for お名前.com” into your language.](https://translate.wordpress.org/projects/wp-plugins/wp-migration-for-onamaecom) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/wp-migration-for-onamaecom/), check out the [SVN repository](https://plugins.svn.wordpress.org/wp-migration-for-onamaecom/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/wp-migration-for-onamaecom/) by [RSS](https://plugins.trac.wordpress.org/log/wp-migration-for-onamaecom/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 2.1.5 * Fix: `find_running_backup()` now ignores stale `pending`/`processing` locks older than 1 hour instead of treating them as an in-progress backup. An abnormally interrupted backup previously left a TTL-less lock in `wp_options`, blocking every subsequent backup on the same site with `in_progress`(409) forever (orphan lock). `AbstractAction::save_job_info()` now stamps `updated_at` on every write so the staleness check can distinguish a genuinely progressing backup (refreshed each batch cron cycle) from an orphaned lock. Root-cause prevention (persisting the batch-side backup_key before run_backup) is handled on the batch side; this change makes existing orphan locks be ignored once they are older than 1 hour( the `wp_options` rows themselves are not deleted), lifting the permanent block( Issue #57). #### 2.1.4 * Fix: Force-update `siteurl`/`home` options at the end of DB restore so that `/ wp-admin/` no longer redirects to the source FQDN. The 2026-02-13 design switch delegated URL replacement entirely to the batch-side `/usr/local/tools/replace- wp`, but in practice that tool does not always land on `wp_options.siteurl`/` home`, leaving them at the source URL. WordPress `wp_login_url()` reads `siteurl`, so accessing `/wp-admin/` on the destination redirected to the source domain’s` wp-login.php`. The original reasoning for removing the delegation („REST API calls aren’t possible after DB restore because nonce/session are invalidated“) still holds for _next_ requests, but synchronous in-request execution via `$wpdb`— the same pattern as `cleanup_restore_files()` — is unaffected. `RestoreFinishTask:: update_target_urls()` is now invoked synchronously inside `RestoreAction::execute_restore_database()`‚ s completed branch to set both options to `target_site_url` (Issue #54). #### 2.1.3 * Fix: AbstractAction::save_job_info() now flushes the WordPress object cache before calling update_option(). The 2.1.1 fix only flushed on SQL import completion in RestoreDatabaseTask, but SQL import is split into BATCH_SIZE=100-statement chunks across multiple HTTP requests (needs_continue) to avoid PHP max_execution_time. This affects any restore where the source site’s SQL dump exceeds ~100 statements— a standard WP install with 15-30 tables (DROP + CREATE + INSERT each) plus chunked INSERTs for large tables typically exceeds this, so the bug can fire even on a first restore if the source is sized normally. Symptom: wp_options gets DROPed/ CREATEd/INSERTed during a chunk, save_job_info is called at the chunk boundary, update_option reads the stale cached value as $old_value, $wpdb->update() returns 0 rows, add_option fallback is also skipped (cache says value exists), so restore_info is never persisted. The next GET /restore/{id} returns 404 Not Found. Flushing before each save_job_info call fixes this and also guards against future tasks that touch the DB (Issue #49). #### 2.1.2 * Fix: Backup now excludes `wp-content/object-cache.php`, `wp-content/advanced- cache.php` (WordPress drop-ins), and `wp-content/mu-plugins/` from archives. Previously these were copied from source and overwrote destination-specific files— the source provider’s Redis/Memcached drop-in config would clash with the destination’s cache plugin config (PHP fatal -> 500), and source-provider-specific mu-plugins( WAF, CDN, security) would overwrite destination-provider mu-plugins that the destination hosting ships (Issue #42). * Fix: BackupDatabaseTask now emits mysqldump-compatible session setup at the head of the dump file (SET NAMES utf8mb4, TIME_ZONE=’+00:00′, FOREIGN_KEY_CHECKS=0, UNIQUE_CHECKS=0, SQL_MODE=’NO_AUTO_VALUE_ON_ZERO,ALLOW_INVALID_DATES‘, SQL_NOTES =0) and restores @OLD_* variables in the footer. This fixes restore failures when migrating from MySQL 5.7 to 8.0, where stricter default SQL_MODE rejected` 0000-00-00` dates (post_date_gmt on legacy sites) and AUTO_INCREMENT=0 rows, and where an implicit TIME_ZONE mismatch shifted datetime values between source and destination (Issue #43). #### 2.1.1 * Fix: RestoreDatabaseTask now flushes the WordPress object cache after completing SQL import. Without this, update_option() on freshly restored wp_options sees stale cached values as $old_value and skips the add_option() fallback, leaving $wpdb->update() returning 0 rows. As a result, RestoreAction::save_job_info() failed to persist restore_info to the actual DB, causing GET /restore/{id} to return 404 right after restore completion (Issue #36). #### 2.1.0 * Fix: restore download fully downloads multi-GB archives by looping Range-chunk reads within a single request. The loop exits when remaining time is below DOWNLOAD_TIMEOUT so it never starts a 30s wp_remote_get with only a few seconds of task budget left. * Fix: backup excluded the plugin’s own work directories (uploads/{brand}-backup, uploads/{brand}-restore) only via a regex that did not match brand names containing underscores (e.g., onamae_mig) — rewrote to use Config::get_brand() so backups no longer pull in their own archives (snowball growth). * Fix: handle_backup / handle_restore now return an error if deleting a stale FAILED job fails, instead of silently proceeding to start() with leftover state. * API change: POST /backup and POST /restore now accept an optional backup_id / restore_id from the caller. The plugin reuses an existing job if one exists, or starts a new job with the supplied id otherwise. Omitting the id keeps the previous behavior (auto-generated id). This lets the batch layer tie a job to wordpress_migrations.backup_key so retries resume the same work directory instead of creating a new one each time. * Security: sanitize_job_id now rejects invalid IDs (returning empty string) instead of silently stripping disallowed characters, to prevent accidental ID collisions( e.g. `a/b` and `ab` both reducing to the same job) and path traversal via externally supplied ids. * Cleanup: remove the unused `continue` field from RestoreDownloadTask::download_chunk() now that the loop is driven by the task’s remaining time. #### 2.0.2 * Remove flush_rewrite_rules() from RestoreFinishTask (delegate to batch-side wp- cli). #### 2.0.1 * Improve error handling: distinguish download_not_found, extract_failed, db_import_failed error codes. * Add SSL certificate verification fallback for backup file download. #### 2.0.0 * Security improvements and codebase overhaul. #### 1.1.0 * Changed Japanese plugin name. #### 1.0.9 * Change file installation function. #### 1.0.8 * Change author. #### 1.0.7 * Supports php8. #### 1.0.6 * Added file installation function. #### 1.0.5 * Bug fix. #### 1.0.4 * Bug fix. #### 1.0.3 * Bug fix. #### 1.0.2 * Fix restore download logic. #### 1.0.1 * Bug fix. #### 1.0.0 * Initial release. ## Meta * Version **2.1.5** * Last updated **2 mjaseca** * Active installations **400+** * WordPress version ** 6.2 abo nowša ** * Tested up to **7.0.7** * PHP version ** 7.4 abo nowša ** * Language * [English (US)](https://wordpress.org/plugins/wp-migration-for-onamaecom/) * Tags * [backup](https://dsb.wordpress.org/plugins/tags/backup/)[migration](https://dsb.wordpress.org/plugins/tags/migration/) [restore](https://dsb.wordpress.org/plugins/tags/restore/) * [Rozšyrjony naglěd](https://dsb.wordpress.org/plugins/wp-migration-for-onamaecom/advanced/) ## Pógódnośenja No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/wp-migration-for-onamaecom/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/wp-migration-for-onamaecom/reviews/) ## Sobustatkujuce * [ Onamae.com byGMO ](https://profiles.wordpress.org/onamaecom/) ## Pódpěra Got something to say? Need help? [Forum pomocy pokazaś](https://wordpress.org/support/plugin/wp-migration-for-onamaecom/)