Last week I was creating a blog for one of my web clients. A quick down and dirty for informational purposes is that what you do is go into your host and create an area for your blog software to be uploaded to. If you’re domain is going to be your blog then you’re pretty much set. However, if you’re going to add your blog to your existing domain, then you need to create a subdirectory within it.


by Niels Hiedenreich

I went into her host account, which is also 1&1, and created the subdirectory. When you do this, you have to make sure you’re creating the subdirectory within the original domain as opposed to creating a subdomain outside of the main domain. No, I’m not even going to try explaining that because it looks and sounds stupid no matter how I might try to clarify it. lol

After 10 minutes I went to check and the new folder was there, all set for me to upload the software. I did all of that, using WordPress of course, and it took just over 5 minutes. I had already prepared myself by going into MySQL and creating a database for the blog, so I opened the wp.config.sample.php file and put the proper information into it, then uploaded it as wp.config.php, as you’re supposed to do.

All seemed to go fine. I went to the link for the blog, created a password, signed in and all looked pretty good; normal, I’ll say. I had gone searching for a few different templates for my client to select from, but I chose one to start with because I know she likes colors. I had to do this conversion thing to switch it from PHP 4.4.9 to PHP 5.2, and once I completed that I installed just a few plugins that I thought were important to start with.

Everything looked pretty good, but I had noticed when I was looking at one of the themes I was considering that there was some error code showing up. I had planned on sending her an email telling her about the blog, but decided to wait until the next morning.

Next morning comes and I try to find her blog; it’s not there. Neither is her website; ouch! Actually, her website was now showing up as a skeleton of what her blog would look like without any pattern or background. Nope, this wasn’t good. I thought that maybe I had done something wrong to the .htaccess file so I went in and deleted that; nothing happened. I reloaded all the blog software; nothing. As a matter of fact, I was now getting one of those Error 500 messages; things seemed to be getting worse.

I decided to delete all the blog files and start again; this was taking forever. When that was completed I tried to go to the main website and now I was getting Error 403. I wasn’t quite sure about that one so I did what I should have done in the first place. I went to the host site and then to their FAQ. I looked up Error 403 and it said that meant the site was being directed somewhere that didn’t exist as the main directory.

Suddenly it all made sense. I went into the domain settings and I had made a mistake. I had created the new directory, but inadvertently told the site that the new directory would be the new main directory instead of a subdirectory of the one already existing. Ugh! Had I checked the stupid FAQ first I’d have saved myself an hour’s worth of headaches. I went back into the domain area, told it that the original directory was the main directory, waited 5 minutes, and the website was back, proud as anything.

After that I reloaded all the blog software, et al, and the new blog is back in service, looking great, and the original website is back as well; whew!

As I look back on this I realize that I wouldn’t have found the error if I hadn’t started deleting some of the blog files. After all, I had that Error 500 thing, and I’ve seen that before. I put in all the tricks I knew of to get rid of it, the simple stuff, and none of that worked. Not a single reference I found even mentioned checking out the directory first. So, if I can save anyone a little bit of time by writing this post, then it’ll all have been worth it.

Digiprove sealCopyright secured by Digiprove © 2011 Mitch Mitchell
Share on Google+0Share on LinkedIn2Tweet about this on Twitter0Share on Facebook0