Previous tutorial gave explanations on how the upgrade backup works, what files to mark for backup and add to the list, what to avoid and what are the requirements for this to work at all. Here you will see the process in action and how easy is to use it.
If you are plugin developer, it’s very important to give as much info about the plugin updates as you can before the blog admins update the plugin to a new version. Also, some of the plugin control panels go into different menus, and it’s a good idea to have direct links on the plugins panel also.
After the first part of the benchmark of WordPress 3.0 versus 2.9.2, here is the second part focusing on the admin section of the WordPress and the execution on the client side. Part 3 is coming in a few days and it will be dedicated to testing on the blog side of the WordPress.
WordPress 3.0 has been released few days ago, and judging from the search queries that brought visitors to this website, the transition has not been without problems. So, here is the first part of WordPress 3.0 benchmark comparing this version to previous 2.9.2.
Here is the first official, and most important stable, release of Dev4Press Updater plugin. Unfortunately, if you used previous version, you can’t perform update with it, because installation was broken in that one, so you need to install this version manually.
Latest beta release of Dev4Press Updater is available. Several problems are fixed and improved, and some major features added including update through cron job and support for xScape themes for auto update. Also, POT translation file is now added to the plugin.
Now that the WordPress 2.8.1 is released, as promised, I have tested this latest version. But I didn’t want to show the same data again, so this time I will test WP 2.8.1 against WP 2.8. Also, for some of not so relevant data I will not use charts. This post will show data from testing both WP administration and actual blog pages.
