Arrgh, fatal error after upgrade to 2.02

Ok, throwing in the towell after poking around various files, going for a fresh install, crossing fingers since DB in myphpadmin shows all info still intact. Wish me luck.

Say – make sure that if you’re FTP’ing files to your server that you are in ASCII mode.

Thanks much for the tip, but I am an antiquity, I used cli with SCO to learn *nix if that gives you a hint on my age, and checked that. I got it fixed with a fresh install, and now am encountering db errors, and wp-content directory not writeable, and the upload error folks are seeing even tho the perms are correct. I suspect it’s something to do with new db tables, new install over existing DB, headed there next.

I will keep twiddling . Thanks again ??

Muahhahha! I think I might have found the bug. Checking my db the encoding is now Latin_Swedish_ci… should be UTF8_general_ci So, I am going to guess there’s something in the upgrade process, or the package that converts DB collation? Now I have to figure out how to fix it back, this could be why folks are getting perm problems etc. I’m a newb with myPHPadmin, so I will report back how it goes.

Ok, I laughed too soon, went through and changed collation back to UTF8_general_ci and that didn’t fix the perm problems. Still can’t upload pics, still can’t use backup features, still can’t write files. hrmmmm

To fix the encoding / collation issue I had to drop the entire db and rebuild, that’s now fixed to UTF-8 all through. Whee!

However, I am still having problems with posting pics, running backup, etc. WP seems to think my wp DIRs are not writeable by server, but I’ve verified through other programs and methods that they certainly are.

I’ve got a support call in to my host, but I really think this might be a wp problem, or something with the way I installed.

Thoughts anyone?

I backed down to 1.5.2, and have zero problems with uploads, perms etc., but I would really like to get 2.02 running.. working with host support services to see what the issue is.