This is the sixth part of How to Transfer a WordPress Site from a Development Server To a Live Server tutorial series. In this session we run importbuddy.php to migrate the development site to the live server. We go through a step by step process on how to do that. It’s important that you have your database name and password when doing this.
How to Transfer a WordPress Site from a Development Server To a Live Server – Part 2 – Install Backup Buddy
How to Transfer a WordPress Site from a Development Server To a Live Server – Part 3 – Copy the Site with BackupBuddy
How to Transfer a WordPress Site from a Development Server To a Live Server – Part 4 – Create a Blank Database on the Live Server
How to Transfer a WordPress Site from a Development Server To a Live Server – Part 5 – Upload Copy to the Site
How to Transfer a WordPress Site from a Development Server To a Live Server – Part 6 – Run the ImportBuddy Script
How to Transfer a WordPress Site from a Development Server To a Live Server – Part 7 – Check Site Functionality
How to Transfer a WordPress Site from a Development Server To a Live Server – Part 8 – Search and Replace Old URLs
How to Transfer a WordPress Site from a Development Server To a Live Server – Q and A
Okay so it looks like everything’s uploaded and we have our database created and everything else. So now what we’re going to do is actually run importbuddy.php. So what we’ve done here is we’ve installed an activated Backup Buddy, we’ve made the Backup and downloaded it. We’ve created an empty database. We’ve uploaded Backup Buddy and Import Buddy to the live site and now we’re going to run importbuddy.php. And the way we run importbuddy.php is to type www.reliefapp.com/ and then it’s importbuddy.php.
Now so you can see what’s going on here, this is the domain name, right? Reliefapp.com and so what’s going to happen is it’s going to look for the file, importbuddy.php and start to run it which is why importbuddy.php is inside the root of the reliefapp.com website.
So we hit enter here. Now, Import Buddy is going to do all the heavy lifting on this transfer. So the first thing we want to do is put our password in, authenticate it, and now it finds that there’s this backup folder. I’m sorry, it finds that there’s this backup zip file to use and so it’s going to let us.. it’s giving us a choice of selecting that. If there were other potential choices that could be used, it would show those as well. We can click on the server information and we can see you know, to what extent it thinks this is going to work and it’s giving us a little warning saying that the php memory limit is at 64 mb and they recommend it being 128. We’re going to run this in any case just to see whether or not… it would probably work fine given the size of the site. But otherwise, we’d need to go in and we’d need to fix this.
The magic quotes really doesn’t really prevent this from working. They say really, your web server ought to disable magic quotes and they are enabled here. But that’s not going to prevent this from working. And if we have some problems, we could choose advanced configuration options where we could you know, come in here and address these things. But at the moment, I think this is going to go just fine so I’m not going to do anything except say next step. But we’ll come back and look at those options if it doesn’t work the first time out. But I think you’re going to discover that it’ll work the first time here which is the way it generally works for me. The only possible caveat for me in this is to say that sometimes, things are funky on GoDaddy.
Okay so this is now telling us that all the files have been succesfully extracted so now we can just go to the next step and it wants to make sure that we know… that this is the WordPress address that we want which is reliefapp.com rather than the old one, relief.tailoringtheweb.com. We could futz around with this but we’re not going to.
Now, on every other server besides GoDaddy that I’ve ever worked on, local host has been the right thing to put here. However, in our situation, local host is not right. We need the actual server name for this mySQL server which is why I opened this up. Because this is actually the name of the server right here, reliefappdb847 blah blah blah. That whole thing is the actual server name so we’re going to copy that server name over to here in place of local host. If you’re doing this on Blue Host or Host Gator or InMotion Hosting or I think…iPower Web you know, any of the big boys, it’s most often, local host is the right thing to put there. The database name here is reliefapp. The database user is the same. The database password is the one that we created and we can test those database settings. And what it’s saying is that it logged into the server, it verified access and permissions and everything else. And so we can just go ahead and go to the next step.
Now it says the database import was complete so we can take it to the next step which is where it’s going to go in and try to fix all these things. And actually, as far as its concerned, this thing is… this import is now 100% complete. We can come back and delete the zip archive and delete any temporary files. Although we’re going to wait until we check very quickly to make sure it is actually working properly.