In upgrading my blog from Wordpress 2.2.1 to 2.3.2 (I may have been a bit behind), I remembered why the process is such a pain in the ass. It’s not that the upgrade itself is difficult — it’s just that more often than not, something will go wrong while I’m trying to get the files from my computer to the server. For example, my FTP client will often freeze and die in between (and I’ve tried multiple ones with the same results). Today, however, my whole domain’s FTP connection went down in between, so the whole upgrade stretched out over two hours when the actual work lasted perhaps five to ten minutes. Nonetheless, I was successful in the end…or so I hope, but feel free to report any possible errors/general wonkyness you might run across!
As for things that I’d been working on over winter break, the poetry section got a facelift and a proper name of its own: Poetica. Sadly, it does not have any new pieces added yet. I finally got the portfolio up as well, although it already has a layout of its own I will be working on to turn it into a full-fledged subsection of the site. I also drew up a new look for the blog, only to scrap it in favor of trying to push myself more design-wise. So in other words, all this time at home has at least been inspiring some site productivity and design!
I *really* recommend the Instant Upgrade plugin: http://www.zirona.com/software/wordpress-instant-upgrade.
V xx
What do you use for an FTP client? I ssh / sftp over my files with WinSCP, a free windows implementation of the scp (secure copy) protocol. It rarely glitches on me.
Well, you could always use Rm — http://www.wirewd.com/hacks/rm/
Elliott: It doesn’t matter what I use, I seem to have the magical touch which makes FTP clients crap out on me during the upgrade. I’ve used WinSCP, WS_FTP, SmartFTP, and Transmit (which is for Mac OS X).
Ken: But I lurve Wordpress, pseudo-warts and all!
I recommend the Instant Upgrade plugin as well