Welcome back to afoe 3.1 – now running on WordPress. What I considered to be a weekend’s job – moving a blog of the size of afoe from the multiblog capable Movable Type to the single blog CMS WordPress and hacking it to the extent necessary to keep the impression of a multiblog – turned out to be just a little more complicated and time consuming.
I’ll write about this in a little more detail in a couple of days, so those among you, gentle readers, who might suffer from the same comment spam/Perl induced server problems, can benefit from my experiences to some extent, should you ever attempt to make the switch.
There are a couple of new features, mostly concerning comment subscription possibilities. Unfortunately, apart from the occasional lack of appropriate WordPress CSS, some things still don’t work, like our aggregator @afoe, which won’t function properly until I’ve renamed a couple of functions in the meneamÃ© and pligg scripts it uses.
But for the moment, I’ll just sit back and wait for your participation – because the most important good news is the following:
Coments are open again – and despite the beautiful categorised permalinks which we are using now, not a single one of your links to any afoe archive page will break…
should you be concerned about the relative silence on afoe while seemingly everyone else is celebrating the European anniversary, I would like to let you know that, afoe is once again in the midst of an important transition: Following the recent comment spam/Perl-related server issues with our host that forced us to temporarily disable the comments in order to keep the site online, I am now porting the blog from Movable Type, the blog CMS to which we have been faithful since 2003, to WordPress, which, as you can probably imagine, is not too simple given the plethora of small functionality differnces, differences in template structures and, not least, the size of the afoe blog family.
For you, I suppose the most important information will be that I am fairly certain we wonâ€™t loose even a single permalink during the transition due to a lot of google research and a hack for the WordPress Movable Type importer that allowed us retain the post IDs once assigned by Movable Type. Thus, at the end of the transition all MT Permalinks will be seamlessly redirected to the respective WordPress entry. No need to adjust any of your links.
So, if all goes well, we will be able to reactivate the comment functionality in a day or two, and hopefully, you wonâ€™t even notice that weâ€™ve switched to WordPress.