artscenter

I see. Thanks.

Thanks to “whooami” for the info about which files changed from 2.3.2 to 2.3.3, and for making them available as a .zip on his own site.

BUT this info should have been included in the developer’s blog that announced the release. It would be nice to also have an “official” .zip (and a .tar.gz) of the five files. That way we could be assured that the info was correct, that the .zip included the correct files, and that they had not been tampered with.

It looks like “whooami” has done a lot of great work helping people get WordPress working, but there’s nothing to prevent a malicious person from posting a bogus .zip file that includes malware of some sort. Without an “official” .zip file, we each have to decide on our own whether or not to trust “whooami”‘s version.

(I’m not trying to cast any doubt on his work, but as far as I can tell, he isn’t officially part of the WordPress development team, or even a moderator. If his information was wrong, I assume somebody official would have seen it and removed his post. But his website could have been hacked at any time, for example, and who would know?)

Me, I’m paranoid: I downloaded the full 2.3.3 installation .zip, expanded it, and took the files from there. That way I knew that they were the correct versions. It probably took me an extra minute or two. (I assumed “whooami” is right about the five files, but figured it was unlikely that updating them would mess up the blog. I backed up everything before doing anything, of course, just in case.)

I do NOT mean this post to cast any doubt on “whooami” or his posts; I just think it would be better to get this information and the files from an official source. And again, thanks to “whooami” for getting this info to us.

I figured out what’s causing this problem: the upgrade killed the wp_postmeta database table. (MySQL “error #1016 – Can’t open file: ‘wp_postmeta.MYI’ (errno: 145)” when I try to access it from phpMyAdmin.)

Somehow WP is still more-or-less working, which is amazing.

I’ll back out of the upgrade and try again.

I figured out what’s causing this problem: the upgrade killed the wp_postmeta database table. (MySQL “error #1016 – Can’t open file: ‘wp_postmeta.MYI’ (errno: 145)” when I try to access it from phpMyAdmin.)

Somehow WP is still more-or-less working, which is amazing.

I’ll back out of the upgrade and try again.

Thanks for your prompt reply.

I’m not sure it’s a problem with generating the thumbnails; they’ve already been generated and are in the uploads folder. It’s more of a problem accessing the existing thumbnails. Did the naming convention for thumbnails change from version 2.0.2 (which is what I upgraded from) to 2.3.2?

My host uses , if that matters.

According to phpinfo, PHP version is 4.3.11, GD is enabled, and is version “bundled (2.0.28 compatible)”, FreeType Linkage is “with FreeType”, and all the GD stuff is enabled (GD Support, FreeType Support, T1LibSupport,GIF Read Support, GIF Create Support, JPG Support, PNG Support, WBMP Support, XBM Support).

(Thanks for the note about 2.3.3; I installed the security fix from it by uploading the new xmlrpc.php. Any way to find what other files have changed? I can’t seem to find release notes for 2.3.3 that list the modified files.)