Upgrading WordPress Woes
Since I play around with websites a lot and am loving WordPress to pieces, I thought I would start a log of blogging headaches.
I went to bed last night and my two sites were running just swimmingly. Beautiful, I thought, as I drifted off to sleep worry-free. When I woke up, I walked into a nightmare. All I saw, no matter where I tried to go, was “ERR0R 500 INTERNAL SERVER ERROR”. Well, didn’t that just slap me in the face? Not just this new site but my old one AND MY STORE!
I done went and broke everything in my sleep.
After researching around, it seems that others who have my host (1and1 hosting services) have experienced the same problem.
The problem: I am using PHP5.0 for my sql databases to run WordPress and it seems that there was a memory issue. One fix that I found that worked for some folks (but not me, unfortunately) was to create a file called “php.ini” (no quotes) in notepad and paste this into your wp-admin folder:
memory=20MB
As I said, that didn’t work for me. So I went searching and found my solution, which was to create a new .htaccess file. Open note pad and paste this into the main directory of your wordpress installation (mine is ./blog and ./home):
<files .htaccess>
order allow,deny
deny from all
</files>ServerSignature Off
<files wp-config.php>
order allow,deny
deny from all
</files># BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^/wp/(.*)$ /wp/index.php?$1 [L]
</IfModule># END WordPress
Options All -Indexes
AddType x-mapp-php5 .php
AddHandler x-mapp-php5 .php
And that solved everything for me. Now, I did have everything beginning with #BEGIN WordPress in my file and it was working, so I don’t quite understand how the top few lines of allow/deny language fixed anything—but they did, so I won’t think about it too much.
Anyway, if you’re having issues with your wordpress site being broken by 500 server errors, try those things out.







Recent Comments