Hi all. I’m attempting to pull a large WPE site to local for the sole purpose of testing MySQL 8 compatibility.
Site is a large media property with around 150GB of data, mostly in wp-content. Obviously not ideal to pull all of it.
I first tried to create a .wpe-pull-ignore file as per:
I dont want certain folders to be pulled or pushed from WP Engine
Is there any way we can exclude certain folders from being pulled or pushed? something like gitignore where it ignores the files/folders when pushing to GitHub
… and placed it in the site root (same directory as wp-config, etc) as the top level directory I can access via SSH or SFTP.
Unfortunately that seems to be completely ignored. Unanswered tickets here (
WPEngine's `.wpe-pull-ignore` not being respected when pulling in a remote site) suggest I’m not alone in that.
I then attempted to do a partial pull, as per:
This appears to work - I can initiate a blank WP site, pull up the file browser, deselect the folders from wp-content that should be skipped. But then on clicking the Pull button the interface disappears - either nothing happens, or nothing happens that I can see.
Has anyone managed to successfully do a selective / partial pull from WPEngine to Local, or does anyone have any ideas why the partial pull seems to fail as above.
Any advice appreciated. Thanks,
Operating System (OS) and OS version:
Generally speaking for large sites we recommend downloading a backup and direct importing that into Local.
You could also use a free plugin like WP Migrate Lite to create a partial backup of just what you need to pull down.
Thanks to the seamless integration of WP Migrate and Local, moving a complete working version of your site from a remote server to your local machine can be done in…
Est. reading time: 2 minutes
Thanks for the pointers. For anyone else in the same spot, I managed to import by:
Downloading the ZIP from wp-engine
Removing a large number of folders from wp-content
Zip again and import that more minimal ZIP
The result was… half working?
But I found that for some reason the WP-Engine DB dump included two copies of the database, in two schema, and Local was using the wrong (outdated) one.
So then if you hit that problem:
Edit the local site wp-config to set the correct schema in $table_prefix
Edit the wp-options table in that schema via Adminer to set the site URL
After that, the site came up correctly in Local.
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.