wasnt nate

Upgrading to WordPress 3.4

I just performed an upgrade from WordPress 3.3.2 to 3.4 and it was a little rocky but not to bad.

One failure that I encountered, on both this site and another blog also hosted via GoDaddy; was error 500. Likely that was due to a timeout on this slow server. This resulted in the following message being stuck on the home page: Briefly unavailable for scheduled maintenance. Check back in a minute.

To resolve this issue just FTP to the root of your hosted content and delete the “.maintainence” that exists at the root of WordPress installation.

While looking up the answer, it seems a few people complain that they cant find this file. To take a random stab in the dark these people are on Linux/OSX machines. On nix style systems a file starting with dot is a hidden file. Use ls -lh to find it

Leave a Reply