Stops the build safely if core\/a plugin\/a theme is updated mid-build \u2014 previously this silently produced a corrupt package that could fatal the migrated site.<\/p>","1.0.5":"
Moves the plugin to its own top-level Site Migrator menu with Export and Import submenus.<\/p>","1.0.4":"
Confirms compatibility with WordPress 7.1 and documents the plugin's external network request in the readme.<\/p>","1.0.3":"
Locks down the package storage directory against direct web access, stops shipping runnable PHP files into uploads, and moves all database work to $wpdb->prepare().<\/p>","1.0.2":"
Renames the plugin to Flexa Site Migrator, prefixes all identifiers to avoid collisions, and hardens database queries against identifier injection.<\/p>","1.0.1":"
Adds a pre-migration system check, one-click cleanup, and single-zip package download; fixes database import on MySQL 5.7+\/8.0 and installer.php downloads.<\/p>","1.0.0":"
Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3660065,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3660065,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3660065,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3660065,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.4","1.0.6"],"block_files":[],"assets_screenshots":{"screenshot-1.jpg":{"filename":"screenshot-1.jpg","revision":3660065,"resolution":"1","location":"assets","locale":"","width":1170,"height":658},"screenshot-2.jpg":{"filename":"screenshot-2.jpg","revision":3660065,"resolution":"2","location":"assets","locale":"","width":1170,"height":658},"screenshot-3.jpg":{"filename":"screenshot-3.jpg","revision":3660065,"resolution":"3","location":"assets","locale":"","width":1170,"height":658},"screenshot-4.jpg":{"filename":"screenshot-4.jpg","revision":3660065,"resolution":"4","location":"assets","locale":"","width":1170,"height":658},"screenshot-5.jpg":{"filename":"screenshot-5.jpg","revision":3660065,"resolution":"5","location":"assets","locale":"","width":1170,"height":658},"screenshot-6.jpg":{"filename":"screenshot-6.jpg","revision":3660065,"resolution":"6","location":"assets","locale":"","width":1170,"height":658}},"screenshots":{"1":"Build the migration package on the production site (Site Migrator \u2192 Export) \u2014 the database and files are exported in chunks with live progress.","2":"Pull from production via link \u2014 paste the pull link on staging (Site Migrator \u2192 Import), test the connection, and start the migration.","3":"Automatic migration in progress on staging \u2014 the package is downloaded, extracted, and the database imported with search-replace, all in one run.","4":"Standalone installer \u2014 the system check verifies PHP, required extensions, archive parts, and the database connection before anything is touched.","5":"Standalone installer \u2014 enter the staging database details, table prefix, new site URL, and directory path.","6":"Migration complete \u2014 a one-click cleanup deletes installer.php, the archives, database.sql, and manifest.json for security."}},"plugin_section":[],"plugin_tags":[151,2814,9055,4155,19979],"plugin_category":[59],"plugin_contributors":[255540],"plugin_business_model":[],"class_list":["post-356515","plugin","type-plugin","status-publish","hentry","plugin_tags-backup","plugin_tags-clone","plugin_tags-duplicate","plugin_tags-migration","plugin_tags-staging","plugin_category-utilities-and-tools","plugin_contributors-flexatech","plugin_committers-flexatech"],"banners":{"banner":"https:\/\/ps.w.org\/flexa-site-migrator\/assets\/banner-772x250.png?rev=3660065","banner_2x":"https:\/\/ps.w.org\/flexa-site-migrator\/assets\/banner-1544x500.png?rev=3660065","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/flexa-site-migrator\/assets\/icon-128x128.png?rev=3660065","icon_2x":"https:\/\/ps.w.org\/flexa-site-migrator\/assets\/icon-256x256.png?rev=3660065","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/flexa-site-migrator\/assets\/screenshot-1.jpg?rev=3660065","caption":"Build the migration package on the production site (Site Migrator \u2192 Export) \u2014 the database and files are exported in chunks with live progress."},{"src":"https:\/\/ps.w.org\/flexa-site-migrator\/assets\/screenshot-2.jpg?rev=3660065","caption":"Pull from production via link \u2014 paste the pull link on staging (Site Migrator \u2192 Import), test the connection, and start the migration."},{"src":"https:\/\/ps.w.org\/flexa-site-migrator\/assets\/screenshot-3.jpg?rev=3660065","caption":"Automatic migration in progress on staging \u2014 the package is downloaded, extracted, and the database imported with search-replace, all in one run."},{"src":"https:\/\/ps.w.org\/flexa-site-migrator\/assets\/screenshot-4.jpg?rev=3660065","caption":"Standalone installer \u2014 the system check verifies PHP, required extensions, archive parts, and the database connection before anything is touched."},{"src":"https:\/\/ps.w.org\/flexa-site-migrator\/assets\/screenshot-5.jpg?rev=3660065","caption":"Standalone installer \u2014 enter the staging database details, table prefix, new site URL, and directory path."},{"src":"https:\/\/ps.w.org\/flexa-site-migrator\/assets\/screenshot-6.jpg?rev=3660065","caption":"Migration complete \u2014 a one-click cleanup deletes installer.php, the archives, database.sql, and manifest.json for security."}],"raw_content":"\n
Flexa Site Migrator migrates a WordPress site from production to staging<\/strong>. It builds a package made of one or more Key features<\/strong><\/p>\n\n Deployment methods<\/strong><\/p>\n\n Method A \u2014 Pull via link (simplest):<\/em> Install the plugin on both production and staging. Build the package on production, copy the link, paste it on staging under Site Migrator \u2192 Import, and click Pull & Migrate. Staging downloads the files from production (byte-range supported) and runs extraction, DB import, and search-replace on its own.<\/p>\n\n Method B \u2014 wp-admin import:<\/em> Copy the package folder to staging's Method C \u2014 Standalone installer:<\/em> For an empty staging site with no WordPress. Upload This plugin does not connect to any service operated by us or by a fixed third party, and it sends no data anywhere on its own.<\/p>\n\n The only outbound network request it makes is to the production site URL you paste on the staging side<\/strong> (Site Migrator \u2192 Import \u2192 \"Pull from production via link\"). When you click Test connection or Pull & Migrate, staging contacts that URL to download the migration package (site files and the database dump) you created on production. The request carries the access token from the link, and, if the package is password-protected, the password you enter (sent in a request header). No third party is involved \u2014 both ends are your own sites \u2014 and nothing is transmitted until you paste a link and start a pull.<\/p>\n\n\n No. The whole build and import process runs inside the WordPress admin over normal HTTP requests.<\/p><\/dd>\n Possibly. After the database is overwritten, the users table belongs to production, so you may need to log back in with a production account.<\/p><\/dd>\n The build side is fully chunked, so exporting is safe at any size. The import on staging runs in a single request through wp-admin; for very large databases, check the System check panel and raise Pull links carry an SHA-256 hashed token \u2014 only the hash is stored on production, and the real token stays in the link. You can additionally protect a package with a password and restrict it to specific IP addresses. Always delete the package after the migration is complete.<\/p><\/dd>\n Staging is completely overwritten<\/strong> (files and database). Only use it with a staging site you can safely throw away.<\/p><\/dd>\n Yes. All admin-facing strings (PHP and JavaScript) are internationalized under the archive-*.zip<\/code> files (site files, split automatically), a database.sql<\/code> dump, and a standalone installer.php<\/code>. It works whether staging is on the same server or a different one, and requires no shell\/SSH access<\/strong> \u2014 everything runs through the WordPress admin over regular HTTP.<\/p>\n\n\n
mysqldump<\/code> when available, otherwise pure PHP) and files are compressed in chunks to avoid timeouts.<\/li>\nwp-content\/flexasm-packages\/<\/code>, then run the migration from Site Migrator \u2192 Import.<\/p>\n\ninstaller.php<\/code> and the package files to the site root, open installer.php<\/code> in a browser, enter the database details, and start the migration.<\/p>\n\nExternal services<\/h3>\n\n
\n
flexa-site-migrator<\/code> folder to \/wp-content\/plugins\/<\/code> on the production<\/strong> site (or install it through Plugins \u2192 Add New \u2192 Upload Plugin).<\/li>\n\n
Does it require SSH or WP-CLI?<\/h3><\/dt>\n
Will I get logged out after importing on staging?<\/h3><\/dt>\n
Does it handle multi-gigabyte databases?<\/h3><\/dt>\n
max_execution_time<\/code>\/memory_limit<\/code> in php.ini first, or use the standalone installer (Method C).<\/p><\/dd>\nIs the transfer secure?<\/h3><\/dt>\n
What happens to my staging site?<\/h3><\/dt>\n
Is it translation-ready?<\/h3><\/dt>\n
flexa-site-migrator<\/code> text domain, and a languages\/flexa-site-migrator.pot<\/code> template is included.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.6<\/h4>\n\n
\n
\/languages<\/code> are now loaded (load_plugin_textdomain<\/code>), so translations work outside WordPress.org distribution too.<\/li>\n<\/ul>\n\n1.0.5<\/h4>\n\n
\n
1.0.4<\/h4>\n\n
\n
1.0.3<\/h4>\n\n
\n
uploads\/flexasm-packages<\/code> now denies ALL direct web access (deny-all .htaccess<\/code>); archives, database.sql<\/code> and manifest.json<\/code> are streamed through authenticated admin-ajax endpoints (capability + nonce) or the hashed-token pull endpoint instead of direct URLs.<\/li>\ninstaller.php<\/code> is no longer written into the uploads directory \u2014 it is streamed on demand straight from the plugin's template, so no runnable PHP file ever lives in uploads.<\/li>\nrunner.php<\/code> chunked-import mechanism (a web-executable PHP file in uploads); the database deploy always runs through the authenticated wp-admin AJAX request.<\/li>\n$wpdb<\/code> with prepare()<\/code> \u2014 the direct mysqli_*<\/code> calls were removed from the exporter, importer, and search-replace, and table\/column identifiers are bound with the %i<\/code> placeholder.<\/li>\n%i<\/code> identifier placeholder in $wpdb->prepare()<\/code>).<\/li>\n1.0.2<\/h4>\n\n
\n
flexa-site-migrator<\/code>) for a distinctive, non-generic name.<\/li>\nflexasm_<\/code>\/FLEXASM_<\/code> under the Flexa\\SiteMigrator<\/code> namespace to avoid collisions.<\/li>\n1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n