![]() From this screen, select the database file that you exported from the live server, and click “Go”. Once logged into phpMyAdmin, select the “Import” tab. If you are using MAMP for Mac or a similar program, you should be presented with a similar screen. To login, open a browser tab and type in “ If you are using Xampp, a main menu will pop up, and you will see an option for phpMyAdmin in the sidebar: Now we want to take that same database, and import it via your local server’s phpMyAdmin. Import Your Site’s Database to Your Local Server The database will be downloaded to your PC. Ignore the rest of the custom settings, and click on “Go” at the bottom of the page. You only want to export the database that you made a note of above, so click on that one. You will then be presented with a selection of databases to export: On the following screen, select the “Custom” export method. Once logged into phpMyAdmin, click on the “Export” tab. If you’re struggling to find it, contact your hosting provider – they should be able to help. Here’s where you will find it on cPanel (which the biggest hosting providers all use): Now you need to login to phpMyAdmin, which every good hosting provider offers. That is the name of your database – make a note of it. Just navigate to the root directory of the fresh copy of your site located on your PC, and open up “wp-config.php” in a plain text editor. Fortunately, that information is contained within the files you downloaded. But before we do so, we need to know which database we are actually looking for. ![]() So now we need to grab it and install it locally. Export Your Site’s DatabaseĪt the heart of every WordPress installation is its database, and it is not contained within the files you downloaded. To check that the files have been successfully transferred, open a browser tab and navigate to “ You should see a database error similar to this: 3. If you’re using a Mac and MAMP, follow the same instructions but adjust the local directory to suit. Once downloaded, place that root directory into the “htdocs” folder, which can be found in the location where you installed Xampp (by default, you can find it at “C:/xampp/”). There will also be a bunch of files in that directory, such as “index.php” and “wp-config.php”. If you are in any doubt as to what you are doing, look out for a directory containing folders such as “wp-admin” and “wp-content”. They will be contained in a root directory such as “yoursitename”. Once there, you want to download all files relating to your site. Now you need to grab your live site’s WordPress files and copy them over to your local server.Īccess your live site via FTP. If you are a Mac user, don’t fear – just complete steps one and two in this tutorial instead. ![]() In layman’s terms, you will be setting up a local server that your WordPress installation can sit on. You will be installing Xampp for Windows, and activating Apache and MySQL on your PC. If you haven’t, just head over to that tutorial and complete steps one and two. ![]() This first step assumes that you have gone through the process of creating a local WordPress site. Just follow the simple steps below and you will have an offline version of your WordPress site up and running in no time at all. But on the face of it, copying an actual live site and moving it offline seems like a far more daunting task. If you have also been guilty of carrying out design tweaks on the fly, now is your opportunity to take your experiments offline.Īs you now know, creating a local WordPress site isn’t difficult at all – in fact, it only takes a few minutes. I’ve certainly been guilty of fiddling with my live blog and regretting the outcome. One of the key reasons for doing so would be the ability to test design changes without disrupting the live site. In Monday’s tutorial on creating a local WordPress site, I said that all WordPress users should have a local installation of WordPress on their PC. Update: This is an old article (from 2012), and as such it may contain information that is now obsolete.
0 Comments
Leave a Reply. |