“Wie niet waagt, blijft maagd”, as they say over here. This guy promises to ask his spam buddies to stop comment-spamming, als long as you put a link to his site. A while ago, he used to promise only “If you dont like advertising comments please send me an email with your site address to tedirectory(at)yahoo(dot)com and I will not write on your site” (cf yahooinsiders), but now he seems to have expanded his influence. He is spamming several of my websites continuously. The source seems to be some people over at Global Net Access, Atlanta (via spam.tinyweb.net).

Which makes me dream of ‘Big Spammer’, a TV-show where known spammers are followed by a hidden camera for a couple of weeks (’see how he has been wearing the same shorts for a whole week now’) after which they are sued, convicted and dragged to jail, while all their computers are crushed by a huge truck. Mmmm, revenge …

Related posts:

1. Avoiding wiki spam in Mediawiki The great thing about Wiki’s is that everyone can...
2. Why spam opt-out lists won’t work I was reading about a technique to discourage spammers:...
3. Don’t unsubscribe from spam Brian McWilliams, author of Spam Kings has published an...

K2 Sidebar modules

The K2 theme comes with this plugin installed and it is the perfect sidebar framework:

• it has an HTML, navigation, RSS, calendar … block and if you really need to do something very specific, there’s always the PHP block.
• per block you can decide on which type of pages it should be displayed. E.g. you can show the navigation only in the static pages, and your recent comments only in the blog section. You can even exclude the showing on individual pages (e.g.: if on one page you need an IFRAME of 800 pixels wide, you can disable all sidebar modules.)
• the blocks show the name that you gave them: you don’t have blocks named ‘Text 1′, ‘Text 2′ but e.g. ‘About’ and ‘Adsense’. This is much clearer if you want to change the order afterwards.

Just compare this: the RSS block for K2 and Widgets:

Which is why I dove into the Wordpress forums to find a way to disable those simplistic widgets and get my original sidebar back. Here is the trick: the disable-wordpress-widgets plugin (also on code.google.com - via wordpress.org) disables the Widgets. I then installed the lastest stable version of K2 (0.9.6) over my Wordpress 2.2.1 and not only are the sidebar modules active again, the sidebar was recovered as it was (from the database, probably). Awesome! Throw out those widgets!

Related posts:

1. Test your karma early in the morning The “Wordpress Automatic Upgrade plugin”“: if it works flawlessly (like...
2. Create your own Wordpress plugin Wordpress has a really nifty system for adding functionality:...
3. My 10 essential Wordpress plugins Since I’ve been doing quite a lot of Wordpress...

However, when it doesn’t work as expected (like yesterday morning here on blog.forret.com), it can be painful. In my case: my K2 template was broken after the upgrade. There is no ‘revert’/'rollback’ function, so you just have to dive in the K2 PHP code and disable the odd line here and there. Once you’re done, you realize that the new version of Wordpress now has Widgets pre-installed, and the K2 Sidebar modules you so carefully handcrafted are gone. So you have to frantically look for the right widgets to do rebuild your sidebar, like the Flickr Badge Widget,the Folding Pages Widget, the Executable PHP widget and Google Adsense Widget. Then you nervously look for the right HTML code for your Adhese ads, and try to get the widgets in the right order. And only then you relax to drink your first coffee of the day (it was 6AM).

Thanks for the tip, Pascal

Related posts:

1. K2 Sidebar modules vs. widgets I upgraded to the latest version of Wordpress recently, and...
2. Create your own Wordpress plugin Wordpress has a really nifty system for adding functionality:...
3. url.rewrite for Wordpress on Lighttpd This blog now runs on a Lighttpd (Lighty) webserver instead...

Whereas Wordpress can automatically adapt the Apache .htacccess file to something like
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
it does not do anything automatically for your Lighty .conf configuration file (which is logical, since an application should not be allowed to mess with a central config file).

So what you have to use is:

1. a Wordpress blog installed in the root of your (sub-) domain:
   $HTTP["host"] =~ "{yourdomain}" {
var.app = "{yourdomain}"
accesslog.filename = base + "/logs/" + app + ".access.log"
server.errorlog = base + "/logs/" + app + ".error.log"
load php app
url.rewrite = (
"^/(wp-.+).*/?" => "$0",
"^/(sitemap.xml)" => "$0",
"^/(xmlrpc.php)" => "$0",
"^/(.+)/?$" => "/index.php/$1"
)
}
2. a Wordpress blog installed in a subfolder (e.g. /blog/)
   $HTTP["host"] =~ "{yourdomain}" {
var.app = "{yourdomain}"
accesslog.filename = base + "/logs/" + app + ".access.log"
server.errorlog = base + "/logs/" + app + ".error.log"
load php app
url.rewrite = (
"^/?$" => "/blog/index.php",
"^/blog/(wp-.+)$" => "$0",
"^/blog/xmlrpc.php" => "$0",
"^/blog/sitemap.xml" => "$0",
"^/blog/(.+)/?$" => "/blog/index.php/$1"
)
}

The xmlrpc.php rule is necessary for external access (like, publishing from del.icio.us or Flickr), and the sitemap.xml file is something for Google Sitemaps.

For those stubborn visitors who always precede their URLs with www, you can also add a redirect:

$HTTP["host"] =~ "www.blog.forret.com" {
url.redirect = ( ".*" => "http://blog.forret.com")
}


Related posts:

1. My 10 essential Wordpress plugins Since I’ve been doing quite a lot of Wordpress...
2. Migration to Wordpress: me vs Murphy Some of you might have noticed my recent domain dance:...
3. WP-Cache speeds up your Wordpress! Ever wondered if you needed a caching plugin for your...

Currently it supports the following features:

1. return the result as
   • REPLACE TAG: replace all occurences of <!--myplugin_tag--> by a certain text/html
   • AFTER/BEFORE POST: add after/before each post (e.g. for tags, DiggMe buttons, Adsense, …)
   • CALL FUNCTION: call the myplugin_showhtml() function (e.g. in sidebar.php)
   • BY PLUGIN PAGE: the result is displayed when the wp-content/plugins/myplugin/myplugin.php page is called (e.g. for results in XML or TXT format)
2. add the result only to posts, pages, search and/or archive pages
3. add a config page to the “Options” or the “Manage” panel
   (here I need to do some work to create a good way to generate the display code and the form processing – showing and changing parameters of your plugin)
4. add optional GPL license text

I of course try to use the guidelines published by Wordpress and Installer. I’ll write something about that later.

A first plugin that I made myself with the wizard is pfmirror. What does this (mini) plugin do? It grabs an external HTML page, replaces all relative links by absolute links (e.g. “images/test.jpg” becomes “http://www.example.com/some/path/images/test.jpg“) and parses only the part between <body> and </body> It then returns the remaining HTML. So I need to execute:
echo pfmirror_showhtml("http://www.example.com/some/path/page.html") (either in a PHP file of the theme, or by using the RunPHP plugin, in any post page).
Obvious improvements that I could do:
- more flexible parsing (show only everything between pattern#1 and pattern #2)
- disable JavaScripts (they mostly don’t work properly when transported anyway)
But most of all, it was a proof of concept of the template generator.

Any suggestions for improving my WP-plugin wizard?

Related posts:

1. My 10 essential Wordpress plugins Since I’ve been doing quite a lot of Wordpress...
2. WP-Cache speeds up your Wordpress! Ever wondered if you needed a caching plugin for your...
3. Test your karma early in the morning The “Wordpress Automatic Upgrade plugin”“: if it works flawlessly (like...

1. WP Installer
   what: install plugins/themes without using FTP
   why: makes installing and maintaining plugins really easy, even behind a firewall. This is the first plugin I always install.
   where: mattread.com
   install: installer-04.zip
2. Akismet
   what: delete comment and trackback spam – not perfect but indispensable – pre-installed on Dreamhost accounts
   why: save you time and annoyance by filtering out the real comments
   site: akismet.com/
   install: akismet.zip (v1.2.1)
3. WP Cache
   what: keep cached copies of your pages – pre-installed on Dreamhost accounts
   why: speeds up your site
   site: mnm.uib.es
   install: wp-cache-2-0-21.zip
4. Brian’s Latest Comments
   what: displays your recent comments in a nicer format
   why: gives a better view of the popular articles
   site: meidell.dk
   install: brianslatestcomments.zip
5. K2 Theme
   what: more than just a theme, includes a WYSIWYG sidebar and customisable header image
   why: if you can live with its looks, the most powerful theme available
   site: getk2.com
   install: k2-091.zip
6. MightyAdsense
   what: manage your Google Adsense code insertion
   why: easily decide what ad goes where without modifying your theme
   site: mightyhitter.com
   install: mightyadsense41.zip
7. RunPHP
   what: run PHP code inside your blog posts
   why: create pages that actually do stuff
   site: www.nosq.com
   install: runPHP2.1b.zip
8. Popularity contest
   what: keep track of # views, comments … of all your posts
   why: makes it easy to show your popular posts
   site: alexking.org
   install: popularity-contest.zip v1.2.1
9. Ultimate Tag Warrior
   what: add tags/keywords to your posts (Technorati compatible), show related posts based on those
   why: last tagging plugin you’ll ever need
   site: neato.co.nz
   install: UTW3-141592WP2.zip
10. Google Sitemap generator
    what: creates a Google Sitemap XML file automatically
    why: because you need it, and you won’t do it manually anyway
    site: arnebrachhold.de
    install: sitemap.zip v2.7

And some nice to have’s:

• FlickrRSS: show Flickr photos in your sidebar
• Gravatar: show avatars for commenters (currently under reconstruction)
• Sparkstats: show blog and comment activity
• Backlinks: show incoming links trend
• Dagon Sitemap: list all posts per category (index or sitemap)

Related posts:

1. Create your own Wordpress plugin Wordpress has a really nifty system for adding functionality:...
2. WP-Cache speeds up your Wordpress! Ever wondered if you needed a caching plugin for your...
3. Migration to Wordpress: me vs Murphy Some of you might have noticed my recent domain dance:...

Well, I did, so I wanted to find out just how slow it was. I set up an MRTG monitoring system on my Dreamhost account. First thing I did was to add 2 tests:

• the download time of my blog’s home page (which involves quite some PHP/MySQL)
• the download time of a small CSS file on the same site, which involves no PHP

Let’s take a look at the CSS file first:

The green line is my 500ms treshold: everything above it is too slow.You see that most of the time my CSS file can be downloaded faster than that (actually the average is around 250ms). There is the occasional peak, which might be caused by temporary network congestion or a server busy doing other stuff – it IS a shared hosting after all.

Now compare this to the time it takes to get my homepage:

The average was more around 1,5 seconds, that is, until last Monday. On Monday I installed WP-Cache 2.0, a Wordpress (2.0) plugin that saves each delivered page on disk for an hour. So the PHP overhead (including SQL statements to get posts, related posts, comments, blogroll, …) is no longer executed for each and every page request. If that page was requested less than an hour ago, there is a saved copy on disk that is returned immediately instead of re-rendering it. The effect: my average access time has dropped to 302ms.

Let’s show you the immediate effect on a second blog I manage:

This is a ‘DAY’ chart instead of a ‘WEEK’ chart, so you can see the individual samples (every five minutes). How hard is it to guess where WP-Cache kicked in?

Any Wordpress installation, but certainly those with plugins like the Ultimate Tag Warrior (those ‘related posts’ are super, but slow) or Brian’s Latest Comments, could profit from this caching tool. Depending on the traffic, that is: you need at least something like 48 visits/day to see an improvement, if you keep the default expiration of 3600 seconds.

Ricardo Galli has developed a top-notch plugin, that works out-of-the-box with minimal configuration necessary. Make your Wordpress fly, get WP-Cache!

(hat-tip to theblogjoint.com for reminding me I should try it)

Related posts:

1. My 10 essential Wordpress plugins Since I’ve been doing quite a lot of Wordpress...
2. Create your own Wordpress plugin Wordpress has a really nifty system for adding functionality:...
3. Migrating from Blogger to Wordpress 2.0 Ever since I saw the new ‘import from Blogger’ functionality...

It used to be that when you installed Wordpress on Dreamhost, you only got 3 standard themes installed. Now you get a whopping 50: 2exquisite, 534, Abstrakt3c, Almost-spring, Artsemerging, Barthelme, Blue Kino, Classic, Connections-reloaded, Craving4green, Dapit_hapon, Darknight2.0, Daydream, Default, Disconnected, Durable, Fasttrack, Fluidityrs, Fspring_widgets, Greening, Hemmednoajax, Leone, Lush, Milc3, Modern, Newzen_2.0_build_105, Nineshadesgreen, Nolimits, Ocadia, Orchids, Phoenixblue, Plaintxtblog, Pressrow, Qwilm!, Rounded-v2, Roundflow, Rusty, Shadedgrey, Simply-vic, Sirius, Stripedplus, Tbs-blue, Thirteen, Tiga, Typoxp, Unsleepable, Veryplaintxt, Vslider2, Wpandreas03, Wpglass, Wpjeriko01.

Here are some screenshots:

and more themes on themes.wordpress.net

Related posts:

1. url.rewrite for Wordpress on Lighttpd This blog now runs on a Lighttpd (Lighty) webserver instead...
2. My 10 essential Wordpress plugins Since I’ve been doing quite a lot of Wordpress...
3. WP-Cache speeds up your Wordpress! Ever wondered if you needed a caching plugin for your...

PROLOGUE: WHY BOTHER?
I have been blogging since 2004 and have built blog.forret.com up to Google Pagerank 6 and Technorati rank 8000. For the non-bloggers amongst you: it’s an ego thing. I don’t want to start again from a PageRank 0, Technorati rank ∞. So that’s why I didn’t stop until I got it back.

SAGA 1: Blogger -> Bluehost
I started blogging in Feb 2004 through Blogger. I published my blog through FTP, first on www.forret.com, then on a subdomain blog.forret.com (on a shared hosting account of mine). I had already started my migration towards Wordpress from the moment I saw Wordpresss 2.0 supported import from Blogger.
I had taken an account with Bluehost, that I already use for my Argentine Tango ‘tangopedia’ wiki, my dutch poetry blog, my podcast feed validator … The main domain name is smoothouse.com, with a (Wordpress) blog on www.smoothouse.com/blog. This would turn out to be a crucial detail.
I had installed a new Wordpress on peter.smoothouse.com, done the import from my Blogger account (posts + comments – really neat!), and was playing around with themes and plugins to see what I wanted. Then Google/Blogger made the unfortunate decision to mark my blog as a spamblog and consequently mess up my whole blog setup. I was thoroughly pissed off (not having been warned, my template gone …), so I decided to give them the finger and switch immediately. I ‘just’ needed to convert my peter.smoothouse.com blog into a blog.forret.com. How hard could that be? Then I discovered that Bluehost has limits to what it can do on DNS subdomain hosting:

• the DNS servers of your domain (i.e. forret.com) should be the Bluehost ones
• through Bluehost DNS management, you cannot map a subdomain onto an external server, i.e. add a ‘A’ or ‘CNAME’ DNS record. I have a lot of forret web tools running on a Windows server, so I need www.forret.com to keep pointing to that server. With Bluehost, that was a no-go
• a subdomain XYZ.forret.com WILL ALWAYS map to the subfolder /XYZ – you have no choice there. In my case: blog.forret.com maps to the folder /blog. Unfortunately smoothouse.com/blog/ is running from that folder too.

I had no time to lose, so I thought: too bad, there goes the domain name. I went ahead and redirected all requests on blog.forret.com to peter.smoothouse.com. I then figured out I could temporarily switch my forret.com DNS servers to the Bluehost servers, get Bluehost to accept to host forret.com domains and then switch back to my regular DNS provider. Once that was done, I could create a peter.forret.com that mapped to folder /peter, the same location as peter.smoothouse.com.

So this was the situation after 1 day: all my blog posts and comments were imported by my new Wordpress on peter.forret.com, but this domain was virtually unknown, all Google results still pointed to blog.forret.com/… urls.
I got confirmation from Bluehost tech support that there was no way I could map blog.forret.com to /peter. Darn. I tried some scenarios (throw away my Smoothouse blog, merge them, …) but I saw no elegant solution. So I went to step 2.

SAGA 2: Bluehost -> Dreamhost
I ordered a new hosting account on Dreamhost. Which means I now have 3 hosting accounts (not counting my Blogspot blogs) – my parents will be so proud. I already knew that Dreamhost was less strict on the DNS stuff. It is a good idea to host your DNS management with them also, but you don’t have to. So I configured it to host blog.forret.com and equiped it with yet another Wordpress. And then: how does one migrate from one Wordpress host to another? Wordpress cannot import from another Wordpress, because it prefers the database backup on host 1, database restore on host 2 method. So all I needed to do was a backup of my Wordpress database on Bluehost. Unfortunately, Murphy kicked in again and made all my phpMyAdmin backup trials terminate abnormally. It was impossible to get a decent backup, and so I sent another email to Bluehost support. In the meantime I had a brand new, pre-paid-for hosting account, doing absolutely nothing. I was not happy.

Bluehost contacted me a couple of days later with another method to take a database backup. That worked, I did the backup, restored it to my new Dreamhost set-up, copied the theme and plugins and had a perfect copy running. Halleluiah! I also copied all the Blogger-generated archives to a subfolder /blog, so that every URL in Google would still point to an existing page. These ‘old’ static HTML pages still had the old layout, but I didn’t care for that then. I switched DNS for blog.forret.com over to the new Dreamhost server, and lo and behold, everything worked.

SAGA 3: rewrite and redirect
So I had 2 sets of pages:

• OLD: blog.forret.com/blog/2006/03/whatever-title-was.html, my Blogger archive, static HTML files
• NEW: blog.forret.com/2006/03/whatever-the-title-was/ page, dynamically served by my new Wordpress.

Visitors to my ‘old’ pages were still redirected to Blogger when they wanted to add a comment. That was not how I wanted it. So I continued further with my mod_rewrite/mod_alias experiments.
The monthly archives were easy to add to .htaccess in the /blog/ folder:
RedirectMatch permanent /archive/([0-9][0-9][0-9][0-9])_([0-9][0-9])_.*$ http://blog.forret.com/$1/$2/
The root of the folder was also easy
RedirectMatch permanent /$ http://blog.forret.com/
RedirectMatch permanent /index.html$ http://blog.forret.com/
which took care of blog.forret.com/blog/ and blog.forret.com/blog/index.html

But then: what to do with individual posts? The title-to-URL translation by Blogger is different from the Wordpress rules (e.g. Blogger drops ‘the’, ‘a’ and other common words, the ‘é’ is dropped instead of being translated into ‘e’). So I decided on using the ?s= querystring parameter (used for search terms). After some trial and error, I ended up with:
RewriteEngine on
RewriteBase /blog/
RewriteRule ^([0-9][0-9][0-9][0-9])/([0-9][0-9])/([a-z]*)-([a-z]*).*$ http://blog.forret.com/$1/$2/?s=$3+$4 [R,L]
So every post is mapped onto a list of (partial) posts of the same month that contain the 2 first words of the title. It’s not perfect, but the best I could do. Undoubtedly some of my blog URLs that can be found in Google will map to an Error-404 page. Can’t make an omelet without breaking eggs.

So this was my struggle with Murphy’s Law. It took me slightly less than 2 weeks to get everything sorted out, but here I am back, on my beloved ‘blog.forret.com’ domain. One thing was really easy: my blog feed. It is managed through Feedburner, so stayed the same during the whole procedure. I had to change the source feed URL a couple of times, but my subscribers should not have noticed too much.

Related posts:

1. Blogger snafu: emergency migration to Wordpress One of the reasons why I have been posting less...
2. Migrating from Blogger to Wordpress 2.0 Ever since I saw the new ‘import from Blogger’ functionality...
3. WP-Cache speeds up your Wordpress! Ever wondered if you needed a caching plugin for your...

So I was just writing a piece on how Google bought Writely with my w.bloggar local client, and when I publish I get an error: “Post was saved as draft, please log in to http://www.blogger.com/ to publish it“. Weird, never have that normally. Anyway, I log in, get the Blogger CAPTCHA ‘word verification’ box and I publish. But I see no changes on blog.forret.com. I publish again. Nothing. Then I click the ‘View Blog’ tab in my Blogger interface. This is what I see:

Apparently:

• my blog is now published to some new awkward blogspot location.
• my template is gone
• the new template advises me to discover wordpress.org

Somewhat startled I dive into my Blogger interface again and the damage is as follows:

• my blog has been marked as a spam blog – YOU %**@!?! (after all I’ve written on spam, I’m not too happy with that)
• I need to do word verification for each post I do
• my FTP publishing settings are gone and replaced by the meaningless blogspot location
• my template is gone and replaced by the “Discover Wordpress” placeholder

Instead of putting effort into restoring my Blogger set-up, I’ve decided to switch as of now to my new Wordpress set-up. Unfortunately this means I have to change my URL to peter.forret.com . This totally sucks, I know. The blog.forret.com URLs should be redirected to their new locations, and I might switch back to the old URL once I figure it all out. For now, here I am, bigger, better and quite pissed at Google/Blogger.

Related posts:

1. Migration to Wordpress: me vs Murphy Some of you might have noticed my recent domain dance:...
2. Migrating from Blogger to Wordpress 2.0 Ever since I saw the new ‘import from Blogger’ functionality...
3. Setting up a new Blogger site So you want to blog? Blogger is by far...

START SITUATION

• The site was managed with Blogger but published via FTP on one of my own domains. Because my old hosting system did not support domain mapping while serving multiple domains, I had to publish each domain in a subfolder. All blog’s files were stored under www.samoera.com/poezie/.
• The individual posts (one poem per post) were saved as /poezie/[YEAR]/[MONTH]/[TITLE].html (e.g. /poezie/2004/04/02/kwijt-bart-moeyaert.html). I always used “[POEM TITLE] ([POEM AUTHOR])” as title for a post. Since Blogger removes special characters, this means that the file name typically ends with the author’s last name (something I will try to use later).
• The monthly archives were saved as /poezie/[YEAR]_[MONTH]_01_gedichten.html (e.g. /poezie/2006_02_01_gedichten.html).

STEP 1: NEW HOSTING

I have taken an account with Bluehost.com. For $6.95 they offer 10GB storage, 250GB bandwidth and the excellent CPanel/Fantastico combo to easily configure sites, install software and manage your DNS.
My Bluehost hosting is on www.smoothouse.com. I use it already for stuff like the podcast feed validator and other small Smoothouse development projects.
Another option is Dreamhost.com: $7,99 per month, 20GB storage, 1TB bandwidth(!) but a less handy management panel. Don’t pay more than this.

STEP 2: SET UP WORDPRESS

Setting up Wordpress with Bluehost is quite easy: you go to the Fantastico page, select Wordpress, decide on a subfolder name (in my case: “poezie”), click “Install” and all the rest is automatic. After this, the blog is installed on -in my case- www.smoothouse.com/poezie. Later I will have to map the poetry site to this folder (without the /poezie folder showing)
Even if you don’t have the Fantastico wizard, Wordpress is one of the easiest programs to install. Then take one of the standard templates

STEP 3: IMPORT FROM BLOGGER

On the new blog, go to the /wp-admin/import.php page, and give you Blogger username/password. Then select the Blogger Blog you want to import and then let the import wizard run. It will import ALL POSTS and ALL COMMENTS! This is friggin’ awesome! It might take 5-10 minutes if you have a large blog.

STEP 4: MOVE ARCHIVE

Now download your full archive (via FTP with e.g. FileZilla) to your local drive and upload them to where they should be after you moved the domain. In my case: I uploaded them to www.smoothouse.com/poezie/poezie which will be mapped to www.samoera.com/poezie/ once the DNS transfer is done.
The reason for this: all your posts will have new URLs and you don’t want people who find your old URLs in Google and click on them to get a “Error 404 not found” page. So you start by copying them to the new hosting server. We will do some more fancy redirect stuff later.

STEP 5: DNS UPDATE

Now comes the tricky stuff: you want your domain name to point to the new host. So you edit the A or CNAME record for the domain name. This will take somewhere between 1 and 24 hours to propagate.
In my case (Bluehost) this also meant I had to transfer DNS management for all subdomains to Bluehost (i.e. change the SOA records). Bluehost requires you to this because the whole DNS management is linked to the Fantastico wizards. In this case it just meant that it took a while longer. I then mapped the www.samoera.com domain to map to the same /poezie folder I just created.
Once that the transfer is done, all your URLs should continue to work (since you took care of that in step 4)!

STEP 6: CHANGE CONFIGURATION

Change Wordpress root path to www.samoera.com instead of www.smoothouse.com/poezie/ (Wordpress will adapt all links on the blog pages). I removed the index.html from archive root (www.samoera.com/poezie) because a lot of sites link to it and replaced it by a index.php that redirects to www.samoera.com.
OPTIONAL: you can play with Apache Redirect/Rewrite rules to take every visitor to one of the old URLs automatically to the new URL. What I tried was:

### for the archives: easy to do!
RedirectMatch permanent /poezie/([0-9][0-9][0-9][0-9])_([0-9][0-9])_01_.*html$ http://www.samoera.com/$1/$2/
### for the post pages: this would have worked if Apache didn't have a bug
#RedirectMatch permanent /poezie/([0-9][0-9][0-9][0-9])/([0-9][0-9])/.*-([a-z]*)\.html$ http://www.samoera.com/$1/$2/?s=$3
I tried to use the fact that the author’s last name (a quite ‘unique’ word) was the last word before the .html to construct queries like: www.samoera.com/2006/01/?s=tellegen (which shows all posts from Feb 2006 with the string ‘tellegen’ in the text – which almost always translates into 1 post). However, due to a bug in Apache (the ‘?’ before the querystring is always translated into %3f and this results in invalid URLs) I haven’t found the right way to do it yet. I could have used
RedirectMatch permanent /poezie/([0-9][0-9][0-9][0-9])/([0-9][0-9])/.*html$ http://www.samoera.com/$1/$2/ but this maps onto a whole month – or up to 10 poems. Maybe I’ll find some other trick.

STEP 7: EXTERNAL STUFF

Change your Feedburner source to the new URL. Everyone that’s subscribed stays subscribed. Ain’t that neat? You don’t have a Feedburner feed? What, you only had Blogger Atom feed? Shame on you. Go get one!

Related posts:

1. Blogger snafu: emergency migration to Wordpress One of the reasons why I have been posting less...
2. Migration to Wordpress: me vs Murphy Some of you might have noticed my recent domain dance:...
3. url.rewrite for Wordpress on Lighttpd This blog now runs on a Lighttpd (Lighty) webserver instead...

The content in articles is essentially advertising by a third party that we host for a flat fee. I’m not sure if we’re going to continue it much longer, but we’re committed to this month at least, it was basically an experiment. However around the beginning of Feburary donations were going down as expenses were ramping up, so it seemed like a good way to cover everything. The adsense on those pages is not ours and I have no idea what they get on it, we just get a flat fee. The money is used just like donations but more specifically it’s been going to the business/trademark expenses so it’s not entirely out of my pocket anymore.
(from wordpress.org)

Andy Baio (Waxy) broke the news on March 30th, at a moment when Matt was on holiday (and off-line), so he only replied on April 1st, about a thousand angry emails later. His defense is that it was a interesting idea, badly implemented, not followed up and never evaluated. Since Matt does not have the profile of a cash-hungry opportunist, and he’s explaining this to an audience of people that understand these reasons (reads like an IT project management what-not-to-do list), the storm will probably blow over.

Normally this is the kind of situation where one would say: “SEO? Leave that to the professionals!”. But the fact is that here in Belgium, some of the companies that claim to be SEO specialists, use dirty tricks all over. Hidden links, bot cloaking, keyword spamming, <noscript> tricks, the whole shebang. It’s like they read the Google SEO warning page as a guideline. “Hey look! We could put ourselves and other customers on every client’s doorway pages. Neat!”.

Joris just posted another example (Immoweb.be) on his SEO blog. And again the so-called “SEO professional” fooling around is Extenseo, just as it was for Automagazine and Actel. As one can see on their unprotected Javascript hosting site, they recently add VW/MyWay to their customers, so we can expect those homepages to be featured in the Hoe Het Niet Moet (What Not To Do) series soon!

Technorati: SEO – Google

Related posts:

1. Adsense: The long tail of spare change Last year, Google took in about $2.7 billion through...
2. Amy Cross spamming Technorati If you look through the posts under the Technorati tag...
3. Flickr/Yahoo experimenting with new ad format Flickr has been placing contextual advertising on their “tag”...