edcottrell

I found the problem. My database restore file had gotten corrupted, so that all the quotation marks in the database contents were replaced with backticks (`). For obvious reasons, this messed things up, nicely. So, I replaced all the backticks with quotation marks, and everything is back to normal.

Can anyone help me with this? I’ve been through the search results above, and didn’t see anything quite like this situation.

I have tried deleting the cache folder, adding the DISABLE_CACHE definition, turning off magic quotes, etc. No luck. Anybody got any ideas?

HandySolo: Thanks for the diplomatic response. I’m sure the core files work just fine on most setups; it must be something peculiar about the machines I’ve used. I have used three (one Linux configured by a third party, one Linux I configured, and one Windows I configured). None of them have ever upgraded without at least one tweak (adding an include of a functions file or something). I’d be happy to provide more detail to anyone who wants to work on it; the upgrade process is my only complaint about WP.

Chradil: good advice for everyone; thanks.

I got the install package here. I am 100% certain all files copied correctly and that all old files were deleted. I uploaded the index.php that came in the zip file to replace the GPL index.php that was there after installation. (It was just plain text; it was as though license.txt had been copied directly over index.php.) I followed the directions here exactly.

It does work, now, without any apparent problems, even using my highly-customized theme and numerous plugins. The blog itself is at https://www.edcottrell.com/edblog/, if you feel like taking a look. The install process I had to go through was definitely a major hassle, though. At various stages, I got anything from blank pages to a never-ending loop on upgrade.php, which told me, “Your database is out-of-date. Please upgrade.”

Also, I have done numerous clean installs of every version of WordPress from 1.2 to 2.0.2, without problems. Every upgrade I have ever done has been a hassle, though; maybe not this bad, but not good, either. More time needs to be spent insuring the upgrade process runs as smoothly as the install process.

Also, I suppose this is normal behavior (?!?), but the upgrade process replaced the index.php file with the GPL (license). That’s very strange, and not a good idea.

I got it working, but it took a number of changes, which should probably be made with extreme caution:

• Added this line at 2152 of wp-includes/functions.php:
  if(is_object($wp))
• Added this line at 28 of wp-includes/capabilities.php:
  if(!isset($this->roles)) WP_Roles();
• Added this line at 28 of wp-includes/cache.php:
  if(!is_object($wp_object_cache)) $wp_object_cache = new WP_Object_Cache;
• Added this line at 178 of wp-includes/cache.php:
  if(!isset($wpdb)) include('wp-db.php');

I’m sure the above is not the simplest way this could have been done, but it was what worked. Now to fix my template…

Actually, you didn’t do anything. That is the upgrade for (to) 1.5, not the 2.0.2 version. The 2.0.2 upgrade page is in a different directory (not the live site), since it’s not working.

How do I post a new topic on here? I can’t find any link to “new topic” or anything like that…