Posted by Mitch Mitchell on Apr 23, 2012
Last week I tried loading a new blog onto one of my friend’s accounts. I know how the process goes in trying to set up a new blog. You go in and create a new directory, while waiting for it you create a new MySQL account with all the information you’ll need, you go ahead and configure the WP-Config.PHP to what you need, and then when the folder is ready you upload everything and you’re good to go.
Except I wasn’t good to go. The sucker wouldn’t work, and I was getting this strange error message: Your PHP installation appears to be missing the MySQL extension which is required by WordPress.
Only it wasn’t missing anything as far as I could see. I ran a few things and figured something must be up, and at the same time there was a new WordPress update to 3.3.2, so I figured maybe that was the reason. I went and deleted all the files that I’d uploaded and then uploaded the new WordPress, making sure the correct WP-Config.PHP file was there.
I tried it again; same error message. Time to go and do some research, which y’all know I’m big on. And you know what? There’s a lot of mess out there that’s technical gobbledy-gook, and none of it make sense. Okay, some of it made sense, but little of it was anything I could do anything with. I did try some of the things I read, and of course none of them worked.
When all else fails, it’s time to call tech support. I did just that very thing and told the guy who answered the phone what the error message I got was saying. He told me that it was because my friend bought the Windows server package instead of the Linux server package and that, at least with them, WordPress wouldn’t work with the Windows server.
You know, no one tells most people this, but when offered a choice between Windows servers and Linux servers and it’s not your home system, you should always go with Linux. Windows is more stable across the board but not very flexible. I remember my trying to get something to work on someone else’s website some years ago and eventually found out the problem was that they were on Windows servers.
What to do? With 1&1, who he uses and who I use as well, all you have to do is go in and change it in your software package. What happens is that it can take up to 24 hours, though it probably won’t take longer than an hour most of the time, and the account will convert from Windows based to Linux based with no problems. Well, one thing you need to know. Anything you have on your Windows account will be deleted, so you need to back everything up first. Also, any MySQL accounts you’ve created will need to be recreated.
Truthfully, none of that is a big deal. My friend now has his blog, although he’s yet to put anything on it, and everything loaded smoothly. The main reasons I wrote this post is because I couldn’t find this specific information written anywhere and I figured it was time to simplify this stuff. So, if you’re new to this type of thing and you’re going the self hosting route, make sure you purchase the Linux (also known as Ubuntu to some people). And if you’re trying to load a blog and you get that error message above, check to see if you have a Windows package and switch.