
wordpress logo
Yesterday I upgraded my WordPress 2.7.1 version to 2.8. I approached this with considerable trepidation because I remember how easy it was a few weeks ago to install the blog for the first time. In my experience, anything that is easy to install is hard to upgrade!
So, I took a cautious approach and I’m really relieved I did.
If you are considering upgrading to WordPress 2.8 from earlier versions make sure you back up all your site files and your database first.
Most people I have interacted with over the last 24 hours have had an easy time upgrading, but there is a significant group (me included) who have had problems. It is not clear why these problems have occurred – whether it is to do with hosting platforms or certain plugins.
For anyone considering upgrading, this post by Jeremiah Hoyet, 5 Ways To Avoid WordPress Update Headaches, will give some other useful advice that you should consider before reaching the point of upgrading. I certainly wish I had read this post before heading off to do it for myself.
Towards the end of this post, there is a section specifically on troubleshooting your installation. There are a number of known problems that can occur following an install, especially Error 500 Internal Server Errors. I have found two solutions to this particular issue, that have been effective on my own installation.
Here is what you can do to make your install as safe and easy as possible:
Back-up
Make sure you have complete back ups of all your site files and your database immediately before you start any upgrade process. This is essential in case anything goes wrong and you need to revert to your previous state. Store these files on a different server or on a local drive rather than on the server hosting your installed WordPress. You will likely find an FTP client useful to download all your site files and the WordPress plugin phpMyAdmin is useful for backing up your database quickly.
Deactivate all your plugins
Once you have backed everything up, deactivate your plugins. There are some plugins that are incompatible with the new version of WordPress, or require further upgrade before they will work. Some plugins have also been upgraded as part of the new version. Having them active during the install could cause conflicts.
Do not use automatic upgrade
This does not work consistently on all hosting platforms. I seem to have problems with automatic upgrades for plugins and the WordPress application. While this does work on most platforms, it doesn’t on all platforms.
Download the zip
You can download the WordPress installation files from WordPress.org Download the zip file to your local drive and unzip it on your local drive.
Start deleting
Use an FTP client to go to your remote server containing your blog. Hold your breath and start to delete files and folders. Don’t worry, if it all goes wrong, you always have a back up. Delete the following files in the order given below:
- wp-admin/
- wp-includes/ (except wp-includes/languages if you have an older version installed)
- readme.html
- wp.php
- xmlrpc.php
- licence.txt
- wp-content/plugins/widgets (if you have this installed)
- wp-content/plugins/hello.php
- wp-content/plugins/akismet/
- All other files in the root EXCEPT those mentioned in 6 below.
DON’T DELETE:
- wp-content/
- .htaccess
- wp-content/images/
- wp-config.php
Upload
Now it is time to upload each item in the list below as a separate item. Do it in the following order:
- wp-admin/
- wp-includes/
- wp-content/plugins/hello.php
- wp-content/plugins/akisment/
- wp-content/plugins/index.php
- all the files in the root directory (except wp-config-sample.php)
Login to wp-admin
Once all the files are uploaded, you need to log in to your new install. In your browser, go to wp-admin by typing into your browser: www.yourblogdomain.com/wp-admin/ (changing ‘youblogdomain.com’ with your actual server domain.
Upgrade your database?
If asked to upgrade your database, click the button then log in as normal. If you get an error message, such as ‘unable to find wp-admin’ then delete the wp-admin folder on your server and upload it again.
Plugins
So, every time you have listened to those ’25 Best WordPress Plugins’ posts, and downloaded hundreds of plugins to use on your blog, today is the day that you might regret it! Identify any plugins that need to be upgraded, download them, delete them from your server in your FTP client, then upload the new files. This is a manual install and is the safest and most reliable method to use at this stage.
Activate each plugin one by one. Do not, under any circumstances do a Bulk Activate. You need to test each and every one of the plugins individually to make sure they work and the system remains robust.
Any plugins that do not work (I have had problems with All-in-one-SEO and YARPP), delete from your server, delete from your local drive, download again and upload fresh copies, try again.
Settings
Once you have a running install, check all of your blog settings. Some configuration settings may be missing and will need to be reset.
Troubleshooting
When I first installed version 2.8, I followed the quick process and this resulted in not being able to identify the /wp-admin/ address; so I could not log into WordPress. This is when I followed the procedure above and managed to install a working version of 2.8.
I did have a number of other glitches which were mildly annoying. For example, the Screen Options pulldown would not work on the Dashboard, so I could not set the number of columns I wanted to use; side panels would not open by pressing on the down arrow, automatic plugin downloads and installs hanging and failing to install. These problems appear to have been fixed by the fixes to the Error 500 Internal Server Error issue below.
Error 500 – Internal Server Error
There is a problem that has been experienced by thousands of users who have visited this post. I have updated this section of the post to provide the latest information available to me.
The problem occurs usually when logged in to wp-admin and concerns an “Error 500 – Internal Server Error” message, or failure to load the various administration panels for editing posts, etc.
Causes of this problem:
I was aware of one cause, which is a memory hungry plugin, or a plugin that is constantly checking how robust your install is, such as wp-security-scan 2.7.1. These plugins are not compatible with version 2.8 of the WordPress platform and need to be updated. Some plugins have been updated already to be compatible with the new version. Unfortunately other plugin authors have been slow in updating their plugins.
Thanks to Codedifferent.com for identifying the second problem in their blog post: Codedifferent.com identified that some hosted server configurations run PHP for users without giving permission to change memory usage. This causes version 2.8 to become flaky as it calls on PHP to operate and it has insufficient memory. The blog identifies the solution, which I have reproduced below for your convenience.
Solutions
The solution to the first problem that causes Error 500 Internal Server Error messages is to uninstall any plugins that are not compatible. If you followed the procedure above, you should have a fairly good idea which plugins are affecting your system. There are lists of compatible plugins available but frankly I do not entirely trust these to be accurate with this issue. It is better to be sure that your plugins work on your installation on your server configuration. If you have installed incompatible plugins and can’t get into your wp-admin/ area, connect to your server using an FTP client and physically delete the plugins that are causing the problem (or go through one by one, testing your installation each time until you find the culprit).
The solution to issue two is to create your own PHP.INI file and save it to your /wp-admin/folder. Do this easily by opening a text document, putting the following code in the text document, saving it as ‘php.ini’ and uploading it to your /wp-admin/folder. The code is:
memory=20MB
That is it. Combined, these two solutions should fix any Error 500 Internal Server Error problems and some other irritations.
Other problems?
I have recently added another post about problems with white screen and Error 404 pages. You can find out more by clicking on the link.
A problem shared…
A problem shared is a problem halved.
By adding your own experiences in the comments section you can help other readers to solve their own problems with WordPress 2.8 upgrades and others may be able to help you to solve your problems. So, would you like to talk about it?











