It is bit complicated and boring but in the end I was successful. I had the old version right from December v2.8 and I was avoid the upgrade as the Automatic Upgrade would hang at “Unpacking updates…” So i did a manual upgrade. These are the brief steps how i did it:
- Backup your database to be on safe side. Though I never had to recover from it. Things went right.
- Backup ALL your WordPress files in your WordPress directory. Don’t forget your .htaccess file as well.
- Deactivate ALL your Plugins. This is important.
- Ensure first three steps are completed. Do not attempt the upgrade unless you have completed the first three steps.
- Download and extract the WordPress package from http://wordpress.org/download/.
- Delete the old WordPress files on your site, but DO NOT DELETE
- wp-config.php file;
- wp-content folder; Special Exception: the wp-content/cache and the wp-content/plugins/widgets folders should be deleted.
- wp-images folder;
- wp-includes/languages/ folder–if you are using a language file do not delete that folder;
- .htaccess file–if you have added custom rules to your .htaccess, do not delete it;
- robots.txt file–if your blog lives in the root of your site (ie. the blog is the site) and you have created such a file, do not delete it.
- Upload the new files from your computer’s hard drive to the appropriate WordPress folder on your site.
- Run the WordPress upgrade program and follow the instructions on the screen.
- Update Permalinks and .htaccess. Update your Permalink Structure and merge the custom rules, if necessary, into your .htaccess file.
- Install updated Plugins and Themes. Please review the list of Plugins that work in Version 3.2.1. Check for Theme Compatibility with 3.2.1 and ask your Theme author for any new version.
- Reactivate Plugins
- Replace the wp-config.php file
- Review what has changed in WordPress. Open the Admin Page.
In case if something goes wrong, replace the old files that you had backed up.
All the best!
Recently came across this issue in my team and I decided to publish a blog for the same:
The default php installation limits on upload file size. The default will restrict you to a max 2 MB upload file for safety. Here are the following configuration attributes in php.ini file:
1. upload_max_filesize – The maximum size of an uploaded file.
2. memory_limit – This sets the maximum amount of memory in bytes that a script is allowed to allocate. This helps prevent poorly written scripts for eating up all available memory on a server. Note that to have no memory limit, set this directive to -1.
3. post_max_size – Sets max size of post data allowed. This setting also affects file upload. To upload large files, this value must be larger than upload_max_filesize. If memory limit is enabled by your configure script, memory_limit also affects file uploading. Generally speaking, memory_limit should be larger than post_max_size.
There are two methods two fix this problem.
Method 1: Edit php.ini
Edit your php.ini file (usually stored in /etc/php.ini or /etc/php.d/cgi/php.ini or /usr/local/etc/php.ini):
memory_limit = 32M
upload_max_filesize = 10M
post_max_size = 20M
Method 2: Edit .htaccess
Edit .htaccess file in your root directory. This is useful when you do not have access to php.ini file, like on many web hosting. In this example, /home/httpd/html is considered as root directory (you can also create .htaccess file locally and than upload it using ftp/sftp/scp client):
php_value upload_max_filesize 10M
php_value post_max_size 20M
php_value memory_limit 32M