Thanks for the message and the recommandation. However it would be ok for a simple site but for a bigger one, most of the time I have to use the .daf format for the package with Duplicator which I can’t unzip
The other solution will be to zip myself the site via FTP for example. But then, no need for a transfert plugin
For my own curiosity : do you know why is there this problem between Duplicatir and Local?
It’s tough to say! All Local really needs to import a site is a wp-content and SQL bundled together. So if you have those you can always zip them up and they should drag and drop right into our App. Sometimes with migration plugins, there may be settings within the plugin or directories within the full site that are conflict with the import.
If your site is really large, as you’ve eluded to, that could be part of the problem as well. If you need to do more of a manual migration into Local, the process could look like this:
Unzip the file in a common location, like the desktop. Or use FTP to bring the files to your desktop.
Create a new, blank site in Local. Use whatever username/password you like since you’ll overwrite the DB with this site archive’s dump.
Copy the wp-content folder from the unzipped location to this newly created site’s location
Copy the correct SQL dump to the site root.
Within Local, open the site shell
Import the dump with wp db import
If that works, now Search and replace the domains. wp search-replace ’ https://production.com ’ ‘http:mylocalsite.local’
Thanks a lot for all these explanations!
I will try this later, for the moment I used the quick solution : “preproduction site create”'s option from my hoster.
But I think it will be the best solution for a large site. I already asked Duplicator’s team before and we don’t find a good solution for this…
