Crazy Meds Forum Software Upgrade Status Reports
I couldn't get my act together until around 11:00 this morning, mainly because I thought I wrote that the upgrade would be starting at noon. In any event there was a minor burp during the initial upload of the software, otherwise that part is fine. I don't have an estimated time as to when it will all be finished.
One problem the new version of the software doesn't fix is resizing avatars loaded into the directory via FTP. A lot of the anime avatars exceed the 120x120 pixel limit, and that was occasionally problematic. I found some freeware that resizes batches of files, so they all meet that standard. I've also added a shitload of new avatars. Because of those two events I sorted the avatars into several galleries instead of having the single anime gallery. As always the promise of more of your1 favorite2 anime avatars will be hanging for who the fuck knows how long. Once I'm finished there will be over 3,000 avatars from about 20 different series, so that should satisfy your inner otaku.
3:25 p.m. MT: Look at that. The upgrade to the most current version assumes you are already at 3.x and not 2.3.x So I first need to upgrade to 3.something and then upgrade to 3.1.latest&greatest.
It's a good thing I don't throw anything away.
6:20 p.m. MT: Nope, that wasn't it. I've opened a ticket with IPS tech support.
My guess is the problem has to do with my breaking the forum on 14 June. The message I get is an SQL failure when something runs a query with a select based on a column that exists only in version 3.x of a table that hasn't been converted, so it doesn't have that column. In other words, even though the upgrade tells me it's going to take version 2.3.6 and turn it into version 3.1, when the software actually starts it expects version 3 data.
Why do I think that's my fault? Because whenever I ran the upgrades in a test environment they worked just fine. The only difference now is the funky database that's a mix of old and new tables. It didn't give me any problems, so I didn't know there extraneous tables until it was too late to do anything about them.
So we're off the air until at least tomorrow. The old version comes up just fine, so the fallback is still good.
It's a good thing I don't throw anything away.
6:20 p.m. MT: Nope, that wasn't it. I've opened a ticket with IPS tech support.
My guess is the problem has to do with my breaking the forum on 14 June. The message I get is an SQL failure when something runs a query with a select based on a column that exists only in version 3.x of a table that hasn't been converted, so it doesn't have that column. In other words, even though the upgrade tells me it's going to take version 2.3.6 and turn it into version 3.1, when the software actually starts it expects version 3 data.
Why do I think that's my fault? Because whenever I ran the upgrades in a test environment they worked just fine. The only difference now is the funky database that's a mix of old and new tables. It didn't give me any problems, so I didn't know there extraneous tables until it was too late to do anything about them.
So we're off the air until at least tomorrow. The old version comes up just fine, so the fallback is still good.
1i.e. mine
2that I could find
Posts
No comments:
Post a Comment