Why did my manual upgrade fail?

As usual, I’m going to say that any number of potential issues can arise depending on your plugins and any customization you may have in your theme etc. I manage a number of WP sites and I have rarely attempted to upgrade by multiple version at once without doing it one version at a time … Read more

WordPress plugin DB upgrade

In short, no. But it’s not particularly complicated. Just add a new version_compare block each time you revise the database: $db_version = get_option( ‘my_plugin_version’ ); if ( version_compare( $db_version, ‘1.1’, ‘<‘ ) ) { // Initial update code added in 1.1 } if ( version_compare( $db_version, ‘1.2’, ‘<‘ ) ) { // Additional update code … Read more

Upgrade WordPress Database from 2.6 to 3.2

Upgrade by simply overwriting the new version of WordPress files, you will get the prompt of upgrading the database when logged in. Do backup the files & database before trying to do anything so that you can always revert back to the old state in case something goes wrong. Most probably the upgrade will work … Read more

How to configure site for automatic upgrades

Easiest way: Use mod_suphp instead of mod_php. This should just be a matter of using whatever ubuntu’s package manager is to remove mod_php and install mod_suphp instead. mod_suphp is a slightly modified version of mod_php. It does the same thing, but it sets the user of the apache process to be the same as the … Read more

Missing argument 2 for wpdb::prepare() Issue

That was not exactly change in code, that was change to better inform people they are not using the method correctly. In line with wpdb documentation you need to properly pass values, or they won’t be properly escaped in query. In your case it would turn into something like: $wpdb->prepare(“SELECT id, name FROM %s”, $table_name) … Read more

Site needs massive upgrade – how to proceed?

Check out the Codex on Upgrading Across Multiple versions. Regarding the upgrading steps, it says: If you plan on upgrading across more than two major releases, please consider upgrading incrementally to avoid potential conflicts and minimize the risks of database damage. For example, if you plan on upgrading from 2.5 to 4.1.1, upgrade to 2.7 … Read more