Good christ did that suck.
I need that opening clip of Samir in Office Space, screaming at his steering wheel having what anyone who has ever sat in traffic knows is a perfectly fucking reasonable temper tantrum.
I’ve just spent the better part of 2 hours banging my head against a desk and playing indiscretely with large sharp objects while trying to get xmlrpc to hit this site.
I’ve done a lot of xmlrpc programming. I know it’s not magic. Google docs works beautifully.
The python code is dead simple. Set about four fields and flip the switch.
I was getting 301s. Of all fucking errors, 301s. “moved permanently.” Checked the logs, nothing.
While LOOKING at the logs, I said “ooh, someone’s banging on my site, can’t have that.” So I blocked the ip address from getting here.
Well…
GUESS WHOSE FUCKING IP ADDRESS I BLOCKED!
That’s right, Freak Boy Wonder managed to lock himself out of his own site. That’s some fine police work there Lou.
I was able to log into the wifi network of an unsuspecting neighbor and fix that particular stroke of brilliance.
I spent 45 minutes following threads of php code through the server side interface (which supports Blogger, metaWeblog, Movable Type, and everyotherdamnthing.)
Pulled down the wordpresslib library, thinking that might exist because of some bizarre peculiarity in the wp host code.
Same thing.
*twitch*
Then I had that moment, that one thought that I can almost rely on when things have gone from black to darker.
“Wouldn’t it be stupid if I needed a trailing forward slash on the filename?”
Now, a file path (on a real OS or online) is “blahblah.com/directory/directory/directory/file” The existence of a “/” means that the preceding is a path. If you’re specifying a file, you don’t need one on the end.
*sigh*
UnLESS you’re calling an xmlrpc server (in wordpress only?)
So yes. It’s all fixeded now.
But I don’t feel any better.
Now on to the FTP code.
Tags: Blogging, Programming, Python, WordPress, XmlRpc