Build Your Own Business Website header image

How to Identify and Repair a Hacked WordPress Site – Step 4 – Reinstall WordPress Manually

Difficulty Level -

Filed Under Topics -

Listed Under Lesson Subjects -

Applies to -

Whoops, you've found some premium content!

Watch the opening clip of this video to preview it,
the full video is available to paid members.

So having removed the existing WordPress installation from the hacked WordPress site we can move on to the next step which is to reinstall WordPress manually.

Download WordPress

The way we install WordPress manually is to come over to wordpress.org and download WordPress. Now, if you know you’re using WordPress 3.8 you can do it here but otherwise, you can come over to that one that was the Download WordPress and then look for your release archive and then you can download any version.

I’m sorry, this set is beta and release candidates. This set is the official releases so if you were on 3.7 and 3.6 you could download it here instead but we are on 3.8 so we can just download it from here. We’re going to download it as a zip file.

Upload WordPress

Once we’ve downloaded that we’re going to come back over to our File Manager in GoDaddy and upload it and we’re just going to hit upload. We’re going to add the file and I believe that’s under Downloads and let’s do it by date modified.

Extract Files to Web Root

Here’s wordpress-3.8.zip. So we’ll open that and it’s uploading the zip file here to her site. If we come down here now, here’s wordpress-3.8.zip. What we’re going to do is put a check box beside it and under More, we can choose Extract. We’re going to go ahead and extract it to the web root.

We’re not going to worry about overwriting existing files because they don’t exist in the web root. What this is going to do is actually sit this inside of a folder called WordPress and we’re going to have select everything here and move that back into the web root.

Create Configuration File

So now if we go back to our web root, we have a new wp-admin, wp-content, wp-includes, okay? So what happens when we run her site? When we run her site now, we get this, “There doesn’t seem to be a wp-config.php file. I need this before we can get started.”

So we’re going to create a configuration file here and now’s when we need that database name, username, password and host and table prefix. We’re just going to say go and now we’re going to paste her database information in here and I’m going to do that privately again just so we can protect the security of her information.

Her database name goes in here, username goes in there, her password goes in the password field, her host name comes from the host name field and her table prefix currently is wp3. We’re going to submit this and now it says, “All right, sparky! You’ve made it through this part of the installation. WordPress can now communicate with your database.”, so run the install.

Now, what we’re doing right here is what we used to have to do for every WordPress install, we used to have to all those kinds of things. But at the moment, we don’t really care what this information is because we’re going to end up replacing it so we’re just going to say test site.

I’m going to use a different one and I’m going to automatically generate a password here actually so that password, password, rick@byobwebsite. I’m not going to allow search engines to do it, we’re just going to install WordPress.

View the Site

Now we’re going to log in and it’s byobrick, again. There we go we’re in and we can view the site, it’s just plain old ordinary blank site, right? But for fun, we’re going to check the source and look at the body tag. And it’s got all that class stuff associated with it and so it looks at the moment like it’s operating correctly.

Next up we’ll be reinstalling the old database for this hacked WordPress site.

0 Comments… add one
0 comments… add one

Leave a Comment