Resolving the “Unable to locate WordPress Content Directory” issue

Do you use a WordPress engine for your blog and recently whenever you try the automatic upgrade functionality you seem to get an error such as the “Unable to locate WordPress Content Directory (wp-content)” issue?

Usually when you start upgrading either the WordPress engine or your plug-ins via the automatic upgrade, you might come about the screen below.

 Resolving the Unable to locate Wordpress Content Directory issue

Now upon entering all of your usual details, you might end up with the error below.

 Resolving the Unable to locate Wordpress Content Directory issue

The “Unable to locate WordPress Content directory” message would then pop up. This issue has been bugging me and after trying various fixes such as allowing the directory to have the necessary authorisations or including in codes into the theme files, it just didn’t seem to fix the issue until I came about this solution.

 Resolving the Unable to locate Wordpress Content Directory issue

By using “127.0.0.1” as your Hostname, you will actually inform the engine to locate the LocalHost where your “wp-content” folder resides in.

A Huge Scare

Alright, maybe this wouldn’t be so scary to some people but it was extremely scary to me. It caused me like 5 minutes of blurness and it definitely made my heart beat a little faster. Well to elaborate a little more on this scare was that I usually upgrade this blog (which runs on the WordPress engine) via a plugin which was called “Automatic Upgrade”. This time when I tried, it didn’t work and I installed the new patch or the newer version via the manual way where I had to ftp to my site and then upgrade it.

Things went well on the ftp side of things.

On the blog front, it didn’t go well at all. I started getting loads of *.php errors all over the admin panel and I decided to delete a few plugins until when I tried to log in to my site, it was just blank.

The admin panel didn’t work.

The blog had a blank and white page.

Of course I panicked for a short period until I decided to calm down, delete some plugins and found out that my “wp-super-cache” plugin was the one causing the php errors. Anyway this site is back up again and thanks me being extremely paranoid, I deleted a whole lot of plugins. Ok to be perfectly honest, I deleted all my plugins. So I just spent the last 30 minutes downloading new plugins.

One of the cooler plugins I downloaded was the new “WPtouch iPhone Theme” which transform this blog into something that is iPhone friendly. If you have an iPhone and you happen to browse to this site, you would notice a nicer interface to read through the various posts here.

There are just so many cool WP Plugins around!

pixel A Huge Scare