| 开发者 | instawp |
|---|---|
| 更新时间 | 2026年4月3日 14:39 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | MIT |
| 版权网址: | 版权信息 |
insta-migrate folder to /wp-content/plugins/X-Insta-Key header for all REST API requestsGo to Tools > InstaMigrate in your WordPress admin. The API key is displayed there and can be regenerated if needed.
No. This plugin exposes powerful migration endpoints. Always deactivate and delete it after your migration is complete.
Yes. The search-replace engine correctly unserializes PHP data, performs replacements recursively, then re-serializes with updated byte counts.
Two methods: (1) X-Insta-Key header with the plugin API key, or (2) WordPress Application Passwords via HTTP Basic Auth (requires admin privileges).
manage_network (super admin) on multisite, instead of manage_options which subsite admins may have/files/concat) output restricted to plugin temp directory only/files/search-replace) restricted to uploads directory only/files/upload) destination restricted to uploads directory onlywp-content/insta-migrate-tmp/ to wp-content/uploads/insta-migrate-tmp/ per wp.org guidelines/wp-cli REST endpoint (required exec)/db/fix-prefix endpoint — fixes usermeta meta_key and options option_name values after a migration where the table prefix changed. Prevents users losing roles/capabilities when the sed prefix-rewrite missed single-quoted values./files/concat endpoint — concatenate chunked file uploads on the server (for large archives exceeding PHP upload limit)/files/search-replace endpoint — search-replace strings within static files on disk (CSS/JS/JSON), used for Elementor CSS domain replacement after DB search-replace