I have finally upgraded wordpress to 2.5.
The old version was 2.3.1 ( yeah that old ) and the upgrade was pretty smooth. I didn't use plugins like instant upgrade for this upgrade but I'm thinking of using for the next upgrades.
How did I do it?
I have my own method for this. It's very similar to what they descibe in the official upgrade docs but a bit modified.
Here are the 7 steps I followed:
- backup the database using the backup plugin
- remember ( write a list of) active plugins then deactivate all ( so if any plugin will not work in the new version you can still access the blog and the admin interface )
- make a backup of all files ( assuming current install is in public_html ):
- cp -rp public_html wp-2.3.1_backup
- download and extract the new version ( it will create a wordpress folder so make sure you don't already have one cause it will overwrite the files in it ) :
- wget http://wordpress.org/latest.tar.gz
- tar -xzpf wordpress-2.5.tar.gz
- use rsync to copy the new files over the old files ( note the exclusion of wp-content to preserve the modifications you might have done to themes and plugins ) :
- sync -avz --exclude=wp-content wordpress/ public_html/
- call the upgrade.php script, go to : http://your_own_blog.tld/upgrade.php
- reactivate the plugins you had active before the upgrade
The whole thing took about 10 minutes and there were no problems encountered except for a few plugins that could not be reactivated because they were incompatible with the new version.
What I like about it?
I like the new interface,it seems friendlier, faster, more slick and I was getting bored of the old one.
I don't care much about the dashboard, but I love the way the WYSIWYG editor works.
I think the feature that I love the most is the automatic plugin upgrade but this is also the one that I think it needs more work ( of course there may be others that I did not notice yet )
what id didn't like?
Here are three problems I found with the automatic plugin upgrade:
- the first time I tired it id didn't seem to care that I selected "No" for the "Use SSL" option and it just told me it could not connect.
This was because my ftp server did not have ssl enabled but it was impossible to know this was the cause because it was clear to me from the web interface that it was not using SSL until I went in the code and just run a print_r on the $credentials variable .
I'm not sure why this happened, I guess a bug. I had to go into the database and manually edit the ftp_credentials option and set ssl to 0 and then the plugin upgrade worked.
- It doesn't remember the value of the "Use SSL" option. After I go in to upgrade another plugin the option is set to "yes" even thou in the database it is 0.
- it removes the old plugin first and then tries to install the other. If the new version install doesn't work for some reason you are left with no plugin and you will have to go in and install manually the old way. I think a bettwe approach would be to first deactivate the old plugin, make a backup copy, try to install the new one and if it doesn't work restore the old plugin.
Overall wp 2.5 brings good improvements and great new features but as with any new major version increase there are a few minor details not taken good care of. Waiting to see what the 2.5.1 version wil bring on he bug fixing side.
Have you upgraded yet? what are your thoughts on the 2.5 version ?
A bug exists in the pecl cli script on freebsd that will not permit you to install any pecl package.
The problem is that the pecl script needs pcre.so but the script calls php with -n ( don't use php.ini ) so the pcre.so extension is not loaded.
A quick fix is to edit /usr/local/bin/pecl and remove "-n" from the last line so it will look like
exec $PHP -C -q $INCARG -d output_buffering=1 -d safe_mode=0 -d register_argc_argv="On" $INCDIR/peclcmd.php "$@"
Just one day after the release and we have the first bugs that show up in the FreeBSD errata.
bug #1 Some isolated crashes were reported for arcmsr, the driver for Areca ARC-11xx and ARC-12xx series of SATA II RAID controllers. This problem is still being investigated. Users that have problems are advised to consider backing out the driver update or installing a version of this driver directly from Areca
bug #2 is a kernel bug related to Unix domain sockets. A patch for this problem has been committed to HEAD and RELENG_6, and is a candidate for an errata patch to RELENG_6_2 after further testing.
bug #3 was observer on systems with heavy network activity. the problem seems to be with the kernel memory allocator. A partial workaround for this problem is to add the following line to /boot/loader.conf and reboot:
More details about the bugs in this release on Errata