so i thought it would be simple upgrading wordpress from version 1.5.1 to 1.5.2, by simply backing up the mySQL database, writing over the old files, and coming back up, maybe 5 or 10 minutes. now 7 hours later, wordpress and my blog are back online. yes, you should always have a production and test environment, but i thought i knew what i was doing.
my mistake was simple, but fatal. all i had to do was use phpmyadmin to drop the new blank data, and restore the old data from my last backup. when i tried if first, i got an error #1064, and something about bad syntax. i did a google search, and found many suggestions as bleak as it’s all over, to try a second time. after around five times, i thought if i reinstall the basic components it would work, so i removed mySQL, PHP, phpmyadmin, joomla, wordpress, and started from scratch.
i’m using a very robust server from westhost, and everything seemed to be working. i even installed perl and python for good measure, but when i got to PHP version 4.x and even PHP version 5.x it was failing to install. this is a remote install using a powerful site control panel. on occasion it would time out, but i would in the past log right back in to try the install. after 45 minutes of install/uninstall frustration, i decided it was not my multiple browsers, but something on my host computer. i wrote around 11 AM to westhost support, and finally around 4 PM got the fix.
so now with a clean install of the underlying architecture, i thought for sure i could get wordpress up again, but i got the same syntax error. using a fine text editor, textwrangler, i tried my last attempt to cut and paste the table definitions into phpmyadmin, and that solved the odd syntax errors. i don’t know if the browser upload function added special characters or removed backquotes, or what, but a simple text paste solved my seven hour site down warning.
i will be more dutiful next time i want to upgrade my site technology. i will not blame PHP or mySQL and concentrate only on the application.