Logo F2FInterview

Wordpress Interview Questions

Q   |   QA

After running the WordPress Upgrade, and clicking on the "Have fun . ." link, it says, "It doesn't look like you've installed WP yet. Try running install.php." The problem may be that there is not a user with administrative capabilities.

To fix that, use phpMyAdmin to manually give a user those capabilities:

  1.     First find the ID of the user you want to make administrator by looking in the wp_user table.
  2.     In the wp_usermeta table, for that ID, find the related user_id, and where the meta_key is wp_capabilites, change the meta_value to a:1:{s:13:"administrator";b:1;}.
  3.     In that same table, for that user_id, where the meta_key is wp_user_level, change the meta_value to a 10.

Please note that the prefix on those tables and those two meta_keys utilize your database prefix. So if your database prefix is mywp_ then the two tables will be mywp_user and mywp_usermeta and the the two meta_keys will be mywp_capabilities and mywp_user_level.  

Under certain situations, it may be necessary to cause a database to pass through the upgrade process again. To do that, you need to lower the db_version value in the wp_options table that corresponds to the version you want to upgrade from. For instance, if you want to force the datebase upgrade that happens from 2.0.11 to 2.3 you would change your db_version to 3441. To force an upgrade from 2.5 to 2.8, change that value to 7558.

'''db_version''' for WordPress releases:
3.3.1 = 19470
3.3 = 19470
3.2.1 = 18226
3.2 = 18226
3.1.4 = 17516
3.1.3 = 17516
3.1.2 = 17516
3.1.1 = 17516
3.1 = 17056
3.0.5 = 15477
3.0.4 = 15477
3.0.3 = 15477
3.0.2 = 15477
3.0.1 = 15477
3.0 = 15260
2.9.2 = 12329
2.9.1 = 12329
2.9 = 12329
2.8.6 = 11548
2.8.5 = 11548
2.8.4 = 11548
2.8.3 = 11548
2.8.2 = 11548
2.8.1 = 11548
2.8 = 11548
2.7.1 = 9872
2.7 = 9872
2.6.5 = 8204
2.6.3 = 8204
2.6.2 = 8204
2.6.1 = 8204
2.6 = 8201
2.5.1 = 7796
2.5 = 7558
2.3.3 = 6124
2.3.2 = 6124
2.3.1 = 6124
2.3 = 6124
2.2.3 = 5183
2.2.x = 5183
2.2 = 5183
2.1.3 = 4773
2.1.x = 4773
2.1 = 4772
2.0.11 = 3441
2.0.x = 3441
2.0 = 3441
1.5.x = 2541
1.x = 2540

Note: Use phpMyAdmin to change that value, or use wp-admin/options.php.

Once the db_version is changed, when logging into your blog a link to upgrade the database will be offered. 

In the past one of the upgrade procedures called for deactivating all plugins, but with the core upgrade process released with Version 2.7 you do not need to deactive the plugins. Here's Ryan Boren's explanation as to why:

During the upgrade, your blog is put in maintenance mode and loading is halted at the beginning of wp-settings.php. Nothing really runs, including plugins. The only thing allowed to run is the DB upgrade, which takes care of making sure plugins are not loaded. You don't need to deactivate plugins unless you like turning them back on one-by-one after upgrading to isolate any breakage they might cause. 

If the core upgrade, for example upgrading from 2.7 to 2.71, is not working, one of these solutions might help:

  1.     If the upgrade seems in an endless loop and you are using Memcache object cache backend, upgrade Memcache.
  2.     If upgrading fails due to a restrictive suexec (e.g. some Italian hosts) then try the FS_CHMOD_DIR and FS_CHMOD_FILE in wp-config.php). 

In order to link this F2FInterview's page as Reference on your website or Blog, click on below text area and pres (CTRL-C) to copy the code in clipboard or right click then copy the following lines after that paste into your website or Blog.

Get Reference Link To This Page: (copy below code by (CTRL-C) and paste into your website or Blog)
HTML Rendering of above code: