This is the fifth part of How to Transfer a WordPress Site from a Development Server To a Live Server tutorial series. In this session we upload the backup file and the importbuddy script to the live server via FTP Client. We also explain how to get your FTP information in Go Daddy.
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
Rick: I’m going to pop this up and then I’m going to navigate here over to downloads, I think which I think actually just up one, right? There’s downloads and so I’m looking for Import Buddy 3. Let’s see, let’s just pick the last modified date.
Okay so here is the big backup. I believe that’s it so we are going to take the backup relief.tailoringtheweb.com and we’re going to take Import Buddy 3. And we’re going to upload them to the root of our website, of the next website. That’s going to take a little bit of time because it’s a large file. That has not finished uploading so we’re going to go ahead and continue this. And while that’s happening, I’m going to look at my list of questions here.
Okay, I’m going to answer this question out of order here. But Ken, I’m going to unmute your microphone. Good morning, Ken. How are you doing?
Ken: Good. I’m doing great, Rick. How are you doing?
Rick: I’m doing very well. So I’m not quite sure I understand your question. Would you rephrase that for me?
Ken: Well, I’m… it’s a way for me to understand more generally what you’re doing but you took 2 files like the master file that you saved and then another file. And then you said that you were putting them in a root and I tried to follow your arrow to see if you were actually grabbing those and placing them on one of those upper open windows and I didn’t see you do anything. And then all of a sudden, the ftp was moving and I just wondered what the heck happened there.
Rick: Okay well, maybe there was a little lag between… on the video so that you didn’t actually… because the way I did it was essentially to open up Filezilla. I navigated on the local side and I navigated over to where my downloads folder is which had both the backup which is called backuprelief.tailoringtheweb.com such and such and had that file import buddy. And I had already connected Filezilla to the remote server so I was already hooked up to essentially, reliefapp.com. And so all I did was just select those, right click on it and say upload.
Ken: Oh okay.
Rick: It’s just a typical Filezilla maneuver except that I don’t have a local website that I’m using to make the transfer. So I just made the transfer directly out of my downloads folder into the root folder of that website.
Ken: Okay, the root folder is that lower one on the right? Is that correct?
Rick: Well, it’s currently the… you can see it’s the root folder because if you look at the middle one on the right where it says remote site and then that slash, that slash means it’s the root. That’s as far down as that goes and then if you expand that, you can see it’s got 3 folders inside of it. It’s got a folder called database backups. There’s a folder called cgi and a folder called stats right now. But then it also has these other files in it and one of the files was this backup relief tailoringtheweb zip that I’ve just uploaded. And the other is this Import Buddy 3 and I’m going to just rename Import Buddy 3 right now by getting rid of that 3. So now it just says Import Buddy php. And so this is just a very standard Filezilla ftp action. Does that makes sense?
Ken: Okay, that’s actually… it makes sense and it helps me… I never really understood what root meant so I’m way back at the beginning. But you do good work with teaching us and I’m starting to pick up the lingo. So thank you.
Rick: Okay well and I’ll show you exactly what root is too. Root means different things depending upon where you are. So if I come over here to… we’re going to just look at this topic of root inside of GoDaddy in particular right now. And if we go over to the… let’s see, we want to just look at the file manager. And so we’ve got our file manager here in GoDaddy. If we click on the file manager, we have a couple of different roots. One of them is the root of your hosting account and the root of your hosting account is not accessible by the web. It’s outside of the web server itself but it has the public html folder which is accessible by the web. And so your very first root, if you’re talking about the root of yoru hosting account then what we’re talking about is right here.
Well actually, it just took me… it took me to this html folder. So what it’s really done is it’s not taken me to the root of my hosting account. It’s taken me to the root of this… of the web server and the hosting account which happens to be the root of this website. And the root of the website is where your wp content, wp admin, and wp includes directories are going to be which is what will happen once this is expanded. So when this is expanded, this is going to be the root directory… you’ll see that it’s the root directory of this website, reliefapp.com. And so for all intents and purposes in GoDaddy, this is the root of this website.
There are… you’re more familiar with me looking at Blue Host and Blue Host gives you a little… perhaps, a little more confusing access to various roots, the root of your hosting account, the root of any given website and then what you really think of as the root of your web server which is your public html directory. But… so yes, the term is a little bit confusing and it gets used different ways in different places. It really just means sort of like the main directory of the given topic, whatever it is we’re talking about.
Ken: Okay, that’s a good way to understand it, main directory of the given topic.