And speaking of speaking of software...the company whose internal file transfer was so horrible, who I probably clocked 6 hours screwing with at least....
I guess they work on Saturdays. And shock, there were problems with the update. And who do they call. My boss, since they're one of our first customers, who calls a former tech support now dev who is nice and cranky, who ended up fixing it. Me? I was dead to the world. I feel pretty dumb, since I knew a few of these problems existed and are a result of the update scripts this guy wrote. Up until now I hadn't really reported them and just muddled through the problems. But yeah. Database updates not going through for no explicable reason (I manually applied about.....10 of them myself last night AFTER I left work, because of a feeling in the pit of my stomach something wasn't right.) And then issues with the script that reactivates all the users in the yard for updates (of which there are about 35 modules, times anywhere from 1 to 50 profiles. For these guys, they had about 10, 5 of which were probably old installs that weren't in use anymore. The point of this script is so you don't have to manually go through each profile to activate them for updates.)
So users logged in to errors, which they've basically been trained to call us immediately about. I know at least one install was perfect, because I was testing on it last night.
Blargh. So many freaking steps to these updates, so many places were expected behavior, silently, does not happen. After doing probably 5 of these updates without problems (on customers whose database we actually maintain in our network), of course, it has to go tits up at a customer whose been with us almost since the beginning, and who has always been a black hole of problems.
Oh well, at least I can finally go to the dev and explain that a) the update likes to not execute half of the database statements in it unless run manually (which makes no sense, because same query run through SQLYOG executes just fine), and the update activation script likes to miss two key components of the update when run.
Talking with teh boss I guess it was pretty minor in his eyes. I just feel bad people got woken up on Saturday to fix stuff.