WordPress.org

1. glenf
   Member
   Posted 4 years ago #

   I'm trying to upgrade from 2.0.7 to 2.3.2, and hope this is not a dumb question (I did try to find similar problems in the forum first). I carefully followed the Detailed Upgrade Instructions in the codex, including disabling any plugins. I deleted all appropriate files before the upgrade attempt (i.e. didn't just copy over). I've tried this many times and have to keep reverting back to 2.0.7 because I simply cannot get it to work (I had tried awhile ago with 2.2 or 2.3 and had the same problem).

   So what happens? Well, when I open the wp-admin/upgrade.php page (or any other page), I get this:

   Failed to open page

   Safari can’t open the page “http://blog.tenuousconnections.com/wp-admin/upgrade.php” because the server unexpectedly dropped the connection, which sometimes occurs when the server is busy. You might be able to open the page later.

   My database is set up correctly, because I don't get any database connection errors (note that if I do deliberately set the wrong password or remove the wp-config.php file entirely, I get the appropriate WordPress error page).

   I don't have a .htaccess file, because I'm not using the pretty permalinks. Any ideas? Unfortunately I don't think I can look at the error logs, since I don't run the server. Would this be necessary, to track down what's going on?

   Thanks!

   P.S. My hosting provider is running:
   MySQL 4.1.20
   PHP 5.1.6
   Apache/2.0.52 (CentOS)

2. glenf
   Member
   Posted 4 years ago #

   By the way, with Firefox I don't get any error messages, but the returned page is empty (0 bytes). This is for wp-admin/upgrade.php, index.php, etc.

3. glenf
   Member
   Posted 4 years ago #

   Also, I know I have to update my SQL collection and character sets to be UTF-8, but I don't think this is related to the above problem (is it?). Everything I read on WordPress.org about fixing the special characters seemed to suggest you perform the upgrade first, then fix the SQL database.

4. glenf
   Member
   Posted 4 years ago #

   My service provider was able to track down the problem. A simple fix (probably because of a PHP incompatibility?)... In wp-includes/taxonomy.php, remove the cast to "object", on lines 11-13:

   $wp_taxonomies = array();
   $wp_taxonomies['category'] = array('name' => 'category', 'object_type' => 'post', 'hierarchical' => true, 'update_count_callback' => '_update_post_term_count');
   $wp_taxonomies['post_tag'] = array('name' => 'post_tag', 'object_type' => 'post', 'hierarchical' => false, 'update_count_callback' => '_update_post_term_count');
   $wp_taxonomies['link_category'] = array('name' => 'link_category', 'object_type' => 'link', 'hierarchical' => false);

Topic Closed

This topic has been closed to new replies.